Apart from screaming case, which is for textual macros, i approve.

Ahh, it is the same thing. Rust example surely has some cruft, but mostly for the better. I’m sure not all of it is needed.

Show the alternative, I’ll have a good laugh.

Exactly. If you are a coder and care about ergonomics of layouts, get split programmable keyboard, do not try to find good layout for normal keyboard, they do not exist. I personally do not like the particular keyboard at the picture, but there are many others to choose from and find a good fit for everyone.

Correspondence is quite a weak relation. Very far from one being another.

Proofs can be represented as programs, not the other way around. Also, USA allows for algorithm parents, and algorithms are maths. While I agree with you, your reasoning is not correct.

It has nothing to do with clang being command line. It consists of many binaries, all of them untrusted. Any time new dynamic lib is loaded Mac stops the process and complains. Then you need to do manual stuff, as you can’t automatically trust a binary, for obvious reasons. This happened almost two years ago, maybe clang got apple certificates or some shit to combat the issue. But my point was that every OS update on Mac brings annoying issues for developers.

Depends on what you are doing. My company was using clang for c++ compilation and it was a drag to make all this clicks for each .so every is update. And there is no way to automate the process. And those occasional compatibility breaks didn’t help either.