@ryo >both newbies and professionals There's your problem right there. If it's designed for both newbies and professionals then they are going to stick with that language and not move on to anything else. That's why people are developing trying to develop professional software in languages like Python, JavaScript, and Java even if C/C++ are better choices.
We need to bring back BASIC. It's solely meant for educational purposes and nothing else. Nobody made professional software in it (maybe outside of a few video games, but those can be an exception). And everyone moved on to languages like C, C++, Pascal, and Assembly afterward.
@xianc78 I know, though it's more about picking a language that meets these 5 criteria rather than "pick something easy and fuck the real work" like what most others would do. And the 5 criteria I gave are of benefit for both newbies and professionals (offline documentation, common sense syntax, and so on). You might have noticed that ease of use wasn't even a thing in this article, that would have made my rankings seem very different (and subjective rather than objective).
@ryo >Please no EPUBs, nothing like that! Is there something wrong with the format in general or is it just because it's not adequate for documentation? I use it only for books.
@yasu Proprietary format that can only be opened in WinDOS or macOS only applications. Melon Books once sold me a digital manga that could only be opened using their own proprietary viewer, so from that point on I started to refuse to read any digitally bought books ever again, it's such a scam!
@ryo It's an open format by default but it supports DRM if the publisher wants. The books I download don't have it and can be read with zathura just fine. Still, it's pretty shitty for them to support it. I used to have a small grudge against PDFs due to Adobe, but I guess it doesn't really matter nowadays.
@aa1874 I never worked with the language at all, which is why I excluded it. I didn't work with Ruby much either, but at least I tried to learn it a few times before, I didn't even get to that point with Rust.
@NEETzsche@aa1874@ryo it used to be pretty annoying back when you had to explicitly declare all the lifetimes but they improved it a lot and there's not a lot of gripes I have about it. my main issues with it are matters of preference, like I think it'd be cool if they had done implicit async await rather than explicit, or stuff that hasn't been implemented yet but are being worked on (enum variant specialization, better const generics, etc). the library ecosystem is already pretty great but it doesn't compete with npm. if it was a shitty language people would be able to attack it for something other than being related to trannies