Yes. IIRC, the flavor that I used was MSWLogo.
I don't think there's an std-way of doing it, but the Rust ecosystem has this thing where people usually settle around one library. In this case, it is tokio. Afaik, most async stuff is done using tokio. What little async I've used, it's been using tokio or some library like actix-web that uses tokio under the hood.
Also, side note, I never understood the idea of why golang is ugly. I think it's fine, except for maybe the repeated if err != nil guards. Those are ugly. I wish it used additive types for error handling.
I've always preferred the functional approach to programming, so OOP never really intrigued me. That's one of the reasons why I never liked C++ or Java, but instantly fell in love with Rust. It lets me do a lot of functional style programming, while still being somewhat practical. (I'm looking at you, Haskell.)
My first ever big boy language was C++ (after Basic, and Logo, does anyone remember that lol). I was in middle school, tried to self-learn from learncpp.com, only to realize that I had mostly learned C, with cin-cout instead of printf-scanf. So I just decided to migrate to C. Nowadays, I mostly code in Rust, Go, and Python. But my experience with C has been extremely helpful. Can't say the same about C++ though.
My first ever big boy language was C++ (after Basic, and Logo). I was in middle school, tried to self-learn from learncpp.com, only to realize that I had mostly learned C, with cin-cout instead of printf/scanf. So I just decided to migrate to C. Nowadays, I mostly code in Rust, Go, and Python. But my experience with C has been extremely helpful. Can't say the same about C++ though.
There IS one of these for everything, eh?
KDE is great but do give some "better" distros like Fedora, or EndeavourOS (basically Arch) a try. Canonical, the company in control of Ubuntu, is a little bit shady.
Everyone has listed a lot of reasons, and there's also https://manjarno.pages.dev/ which pretty much sums up all the technical reasons.
I'd just like to add why I switched. I used Manjaro for a couple of years, and suggested it to friends and family for a while. It was fine when it worked. But when it didn't, it was a pain to figure out wtf was wrong. Their forum wasn't helpful, and you can't get help in the Arch forums, because it's just different enough. Also, whenever something broke, their logic was always backwards. Like SSL broke for the 5th time, just roll back your clock guys. It felt like being in an abusive relationship with a distro.
I finally switched to EndeavourOS some 4 years ago, and it's been very smooth ever since. In fact, I've had a good experience with pretty much every distro that I've used long term (e.g. AlmaLinux, Debian, Fedora, and even Ubuntu), except for Manjaro.
I develop open-source code. But that never made me one of the “I hate proprietary software or IT giant corporations” types.
Maybe it should've.
Storage, RAM, CPU usage. I prefer not to have such a large piece of software running for no reason. It might seem silly, but I hate using resources for no reason. I'll rather have 5 lightweight apps running instead of a huge one, of which I'll only use a few parts.
Fair enough. I'm not a professional programmer, so I guess I won't understand your frustration with long term maintenance of Go code. I do agree that it can be unnecessarily verbose. Writing something as simple as an
httpserver takes a long time. Also, the dependency management sucks. It can't seem to decide if it wants to be declarative or not.I do like that it's dead simple though, and that the standard library has most of the basic stuff. I've mostly replaced the need for Python with Go, for small CLI apps. Nowadays, I only use Python when I have to use some specific library, mostly for mathematical computing.