> In the end, I learned (and accomplished) far more than I ever expected - and perhaps more importantly, I was reminded that the projects that seem just out of reach are exactly the ones worth pursuing.

Couldn't agree more. I've had my own experience porting something that seemed like an intractable problem (https://news.ycombinator.com/item?id=31251004), and when it finally comes together the feeling of accomplishment (and relief!) is great.

Mobile

https://github.com/settings/billing/licensing

EDIT:

https://docs.github.com/en/copilot/how-tos/manage-your-accou...

> If you have been granted a free access to Copilot as a verified student, teacher, or maintainer of a popular open source project, you won’t be able to cancel your plan.

Oh. jeez.

Maybe you'll find the resources I link to in the documentation for my project helpful.

https://github.com/ZQuestClassic/ZQuestClassic/blob/main/doc...

Or perhaps you'd find reviewing my usage of asmjit helpful:

https://github.com/ZQuestClassic/ZQuestClassic/blob/main/src...

My main high-level advice would be to have an extensive set of behavioral tests (lots of scripts with assertions on the output). This helps ensure correctness when you flip on your JIT compilation.

You'll eventually run into hard to diagnose bugs - so be able to conditionally JIT parts of your code (per-function control - or even better, per-basic block) to help narrow down problem areas.

The other debugging trick I did was spit out the full state of the runtime after every instruction, and ensure that the same state is seen after every instruction even w/ JIT enabled.

Good luck!

I've come to accept input lag, but mostly play games where it doesn't matter (simple platformers, turn-based games, etc). I know steam link from my home desktop to my ~5 year smart TV is adding latency to my inputs – though I can't tell if it's from my router, desktop, or TV – but I've come to accept it for the convenience of playing on the couch (usually with someone watching next to me).

I know some blame is on the TV, as often if I just hard-reset the worst of the lag spikes go away (clearly some background task is hogging CPU). And sometimes the sound system glitches and repeats the same tone until I reset that. Still worth putting up with for the couch.

Can anyone suggest a good archive tool? The open source project I help run has ~10 years of conversations, bug reports, feature requests, etc. sunk into Discord, and obviously I want to preserve all that (not sure we'll end up leaving the platform, but it's good to have backups anyhow).

Our bug reports / FRs are in forum channels, and I've written a script to extract those and potentially import them into some bug-tracker. But I'd like something good that can archive the entire thing in a reasonable format.

https://www.politico.com/news/2026/01/30/don-lemon-appears-i...

Note, I'm not using my own judgement. I'm no lawyer. But the judge refused Don's arrest on grounds of no probable cause [1][2].

I agree it seems the protestors may have violated that law by forcibly stopping the service (though I think the judge only found cause for 18 USC section 241: conspiracy against rights), but it seems the judge applied some reasonable discretion to exclude a reporter only there to document it and interview those willing to speak to him. I'd be interested in reading his exact reasoning, but I'm not sure he's shared it.

> than a pastor suspected by the left of being involved with ICE

This is besides the point, but: it's not some secret, it's a fact. He works for ICE, and is a pastor.

[1] https://x.com/JonahPKaplan/status/2014435110209122785/photo/...

[2] https://www.law.cornell.edu/uscode/text/18/248

I haven't seen it myself, but I wonder if it conforms to your theory: does the detective in that show have mitigating explanations for his failures?

No kidding! From the wikipedia page:

> Consideration was given to listing the bench as a protected structure but was decided against as there could then have been a requirement imposed on the council to destroy the tree to protect the bench

The game engine I work on (link in bio) developed a custom language for engine customization, but it never had any runtime debugging capabilities. I've been adding that over the last couple weeks.

The language compiles to a bytecode, which is what the engine runs. But the bytecode has no source information.

The easy part was getting source locations for stack traces (associating each generated bytecode with an originating source line of code).

Harder was getting scopes information for displaying function names in those stack frames, and for associating runtime variables per-scope (stack variables, globals, class fields, etc.)

Now I just need to create an expression parser for evaluating expressions at runtime based on the current scope, add breakpoints and step over/into/etc. capability to the engine, then wrap it all together in a VSCode extension.

https://web.zquestclassic.com/zscript/ (this doesn't show what I'm working on, it's just a basic web text editor to quickly test the language. can't run it from here).

hah.