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

It is also a “refactoring”.

Sekiro can jump, climb, grapple and swim. Those kinds of more agile behaviors add a lot requirements and considerations to the engine and content makers.

In many modern environments the second I start scrolling my eyes start to bleed. Yes, I want 60 fps min. That was the first part. The second part is about stability. 20 fps may be enough for typing, but it needs to be 20 fps all the time. Not the average between 1 and 60, it is makes IDEs unusable.

If FPS is NOT an important metric in text editing, you are doing something wrong. Otherwise, good points.

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.

I agree with your sentiment about users sometimes are disingenuous with their fanboyism. But trying to pretend article is saying rust is terrible for refactoring is not a fair argument either. Some library grade code may require more attention, yes. But in most cases it means you would need to do many changes in other languages too, but you’ll discover it in production.