UI looks indeed better. Uses FreeType instead of strike font. One can tune the freetype glyph contrast in the settings as well. And use any freetype font, like Hack (which is what I do use).
Works smoother because of usage of FastTable which replaces the old lists of morphs that got overkill. Actually, Pharo was fast for dealing with that massive amount of morphs. It felt slow because of the amount of stuff it did. But not intrisically slow.
Godot is super easy in 2d if you understand scene-tree-node philosophy and you have nothing agains thier variation of python. API is small, IDE is good, works great on linux.
Personally I'm using it for prototyping, my main engine is UE4 though.
I'm thinking that maybe it's time to create a small but full game with it.
Humour (or humor in American English) is the tendency of particular cognitive experiences to provoke laughter and provide amusement. The term derives from the humoral medicine of the ancient Greeks, which taught that the balance of fluids in the human body, known as humours (Latin: humor, "body fluid"), controlled human health and emotion.
I share this desire, but it's important for end-users to remember that even if a feature seems arcane and unneeded, you're likely using it indirectly through the libraries you use. Take variadic template parameters for example. The average developer doesn't use these. But very popular library features like make_shared would be at least an order of magnitude more code.
And by making library code easier to write, understand, and maintain, we make it more likely that the more obvious features (like filesystem operations, database abstraction layers, new kinds of data structures, etc.) can be written and maintained.
All that being said, there are completely unecessary warts in C++ that need to be cleaned up. The best thing in-the-trenches C++ developers can do to help with this is to improve the software development lifecycle tooling and practices on the projects they are responsible for. Good automation, static analysis, and testing will make the C++ community more agile and more ready to do the much harder work of deprecating and deleting old technical debt. And it's good for the health of the project anyway.
If that's all you want, you might take a look at the `cleanup` attribute for C. It's non-standard, but it is supported by `gcc` and `clang` and is fairly effective.
Moving a team of ~20 engineers from IJ to VSCode for a single technology is a nonstarter. IJ is still the preferred IDE for the backend and works perfect for everything we've used that's not Typescript.
