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.

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 do not know where your “turns out” comes from, but LOL does something similar and you won’t find skilled competitive players in non competitive queue. For top 0.1% queues are still long, though.

Ai generates texts with accordance to material it learned from. So it will be PC gamer, IGN and Kotaku combined.

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.