It is also a “refactoring”.
It is also a “refactoring”.
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.
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.
Each quarter is just 13 weeks. Problem solved.
Apart from screaming case, which is for textual macros, i approve.