stevefolta

Re "c)": No, self-hosting is the biggest temptation, and the worst mistake, for any programming language. It's death to bootstrapping. However, if you do succumb to the temptation to self-host, having a C backend, as Copper does, is probably the best way to handle it.

Someone turned me on to this recently, but mainly it ended up getting me back into Timeguessr. (I'm much better at Timeguessr.)

"If you have a procedure with ten parameters, you probably missed some." -- Alan Perlis

Looks like a new 1.3 release is coming very soon.

I love QBE, but it does have its limitations: - It handles the ABIs for passing and returning structures in registers, but only with superfluous copies to and from the stack. - Can't generate debug info for data. This is probably due to lack of assembler support and/or complexity in the DWARF format. - The line number debug info directives are currently undocumented and don't support inlined functions.

But it's smol, effective, and it doesn't make you deal with phi nodes!

Oh, it _does_ have string interpolation, my bad. Sadly, not by default -- you still have to go back and add an "f" before the string once you've started typing it and then realize that you want an interpolated string. Also, it doesn't always work -- if I define two interpolated string variables in one function, GCC chokes in a way I'm not understanding. And every interpolated string variable consumes 4K of global memory.

Nice! Compiles in 2s on my unexceptional hardware. But it lacks my other main desiderata in a new language: string interpolation and kebab-case.

Hooray! Personally, I'm hoping this'll lead to support for the GPU on Spacemit SoCs.

I’ve often heard “Fontucky” for Fontana CA.

In synthesizers, diodes are used in oscillators to shape triangle waves into sine waves.

But if that's what they want, they may be driving out the exact wrong subset of their devs.