glram

I'd like a language that allows me to explicitly annotate my code for vectorization/SIMD. Too often compilers aren't able to vectorize efficiently because the heuristics don't detect the opportunity.

Professor Strang’s lectures helped me greatly during my linear algebra class. I thoroughly appreciated his clear, coherent lecture style.

On another note, he is such a nice guy. 10/10.

Thanks for the follow-up! I've always thought the TOFU thing was a huge issue: it's hard to verify the first time and rotating server certs is a nightmare.

Are there any products/tools that make this easier? I've noticed that this isn't common even within companies with robust security infrastructure.

Definitely. If you're going for something integrated, Intel/AMD (and maybe x86 in general) are out of the question.

For a PC, though, using ARM can be tough if you're trying to use Windows. I'm not sure how many Windows programs have ARM binaries.

I really like the certificates for SSH idea... I've never thought about this and have always used vanilla keys.

Does anyone have experience using this? Besides giving auditing information, does this have any other benefits?

I think this is another sign that iOS/iPad OS and Mac OS are converging. If I had to guess, once Apple adopts ARM processors for the Mac, there won't be much of a distinction between the two.

This is really nice. Even with code review secrets still slip through the cracks. I imagine this will be quite pricey tho.

Ah I was hoping based on the headline that this would be some sort of analysis of the actual code -- aka a pie graph of the different language features each team member uses. Kinda like an aggregated `blame` :D

This is quite a disappointment indeed. Turns out that compilers only use like 10% of the instructions in x86. While there are some efforts to fix this (at least for SIMD) with better heuristics, I fear that the best way to solve this might be to go with simpler ISAs and drive up the clock speed.