News for hackers. Stuff that matters.
Re:The Adoption of Rust in Business by nevi-me on Tuesday February 07, 2023 @08:14AM (#34692295)
The simpler parts of Rust feel like TypeScript, let's say as long as you're doing simple things as a start and don't worry about threading.

Rust was probably also a lot easier to learn pre-async-await, because one would have to explicitly opt in to multithreading through std::thread.

My first productive language was JavaScript via NodeJS (I learned PHP first, but it was a mess). I did so much with it that by the time I learnt other languages on my own, it was out of necessity.

From a language syntax and concept angle, I'd say Java + Scala were difficult to grok at first. Java for the boilerplate, Scala because I could never understand what the underscore is for.

Kotlin became a breeze and pleasure, then Rust after that. I learnt each language by converting my projects from a previous language to a new one. So that helped me limit the concepts I'd introduce.

Mostly do some calcs, interact with a DB and expose stuff via gRPC. By the time I started with futures, channels and threads, I had gotten far enough programming against a single core.

I often advise people starting out to be gentle with themselves and stick to what they know first. Like other complex languages, one might remain a learner for very long.

Re:The Adoption of Rust in Business by Animats on Tuesday February 07, 2023 @01:27PM (#34696848)
> Rust was probably also a lot easier to learn pre-async-await, because one would have to explicitly opt in to multithreading through std::thread.

Worse, you can use both in the same program, which, while safe, is really complicated.

There's a lot to be said for Go's green threads for routine web back end stuff. They avoid the async/thread distinction, because they're both lightweight and can block.