They wanted me to make some changes and with the normal workflow that's just git commit and git push. With git send-email I have no fucking idea and it got beyond the point where I had enough cared enough to fight the process.

Yeah unfortunately these numbers don't really allow any conclusions to be drawn at all.

Also they're not really related to supply chain security which is more about deliberate subterfuge. I think the interesting stat there would be how many authors are being trusted typically for each crate.

Interesting idea, but your trick is never really going to help (you can store up to 255 bytes instead of 254). Also always using 256 bytes for every string seems wasteful.

I think LLVM's small string optimisation is always going to be a better option: https://joellaity.com/2020/01/31/string.html

Some bad interview questions are like that, sure. But they're supposed to be things you are very unlikely to have done before and can reasonably figure out. It's not too hard to come up with simple questions like that. (Though I will grant many people don't seem to bother.)

Yeah there's a huge difference between "works 98% of the time" and "works 99.8%" of the time, even though they are both "works most of the time".

Wow, that activated some seriously ancient neurons... I just looked up some of the models it supports and surprisingly they were made within the last decade. For some reason there's still a market for cheap dedicated MP3 players.

I guess they cost basically nothing to manufacture and some people might need them...

No, they're inherently optional in Git. There's no way to "check in" a git hook. You have to put in your README

Clone the repo and then please run pre-commit install! Oh and whatever you do don't git commit --no-verify!

You definitely need to actually check the lints in CI. It's very easy though, just add pre-commit run -a to your CI script.

Small nit:

CHERI is even weirder. CHERI pointers store 128-bit capabilities in addition to the 64-bit address we’re used to

The 128-bit capability (actually 129 since there's a tag bit) includes the address. It's 64-bit address + 64-bit metadata + 1-bit tag = 129-bit capability.

Yeah Verilog. That's literally the language people use to design chips and FPGA bitstreams.

Someone has already done it: https://github.com/Redcrafter/verilog2factorio

It's sooo sloooow though.

Those days never existed. Even the first iPhones were like $500 and that was over a decade ago.

These prices are very high but phones last a lot longer than they used to and are improving a lot slower. I just bought a Pixel 8 for £400 which (accounting for inflation) is about the same price as we used to pay for three old Pixels and even Nexuses.

E.g. the Nexus 4 which was considered "mega cheap" was £279 for the 16GB model, which is £390 in today's money.

They're clearly going for price differentiation based on the model year, but you really don't need the latest model to have an amazing phone any more.

Without static type annotations you can only make best effort guesses that are sometimes right. Better than nothing but not remotely the same as actual static types. The LSP you linked works best when you use static type annotations.

Also I would really recommend Pylance over that if you can - it's much better but is also closed source unfortunately.