11–20 of 67 posts
Is Rust old enough for there to be a 'modern' Rust?
I think so? Modern c++ (c++11) came 13 years after c++98. Rust has been released for close to or longer than that depending on your definition of released.
what word are people going to use after modern. it's kind of like using the word new. we don't use modern rust around here anymore, just modern new new modern rust.
I'm planning to learn Rust next, going to start in a week after a job interview I had already lined up at Google.
I worked with many languages professionally (JavaScript, TypeScript, Java, Python, Go, and now Dart) and many others at the university (C, C++, C#)...
...and Rust is very appealing to me. It's a modern language where the dev tools are straightforward, no need to deal with learning 30 years of legacy conventions, great performance that's on pair with C/C++, yet, at the same time high level and easy to read and reason about. The language is still young enough to make a dent in the ecosystem and build stuff for fun without people whining about JavaScript fatigue. It's versatile, so it can be used (at least theoretically) for web backend, frontend, desktop apps, command line tools, systems programming. It has all the good parts from OOP and FP.
Yes, I'm at least partially responsible for having "xyz rewritten in Rust" almost every day in the top list on HN.
One thing in a bit worried about is the job market, I've been paying attention to job adverts for months and I didn't see many companies that I'd like to join that use Rust in my area (Germany).
Learning it and doubling down on Rust feel like a gamble, but at the same time, I can't imagine that Rust will not be one of the most important languages of the next decade.
My first piece of advice is to just start writing code. If you are not specifically interested in super high performance systems level code, my second piece of advice would be to write code that avoids lifetime annotations until you get the basics of the borrow checker down. For me, this meant writing a gRPC API with Rust using `tonic` with a `diesel` based persistence backend and observability with `tracing` and `op…
Maybe I'd reframe it as "just start writing code, and use RC liberally to avoid lifetimes until you get a handle on them."
Also avoid async for that first project too.
Some people need to get with the picture and drop those antiquated 2021 practices. Puke!
I'm actually looking forward to Rust having a few more years under its belt so I can do more than experimentation with it (and yes, I've seen the Oxide stuff, and there is plenty we can call stable right now -- I just want it to be a bit more weathered...).
This looks like a great resource, starred and upvoted. I'm planning to learn Rust next, going to start in a week after a job interview I had already lined up at Google. I worked with many languages professionally (JavaScript, TypeScript, Java, Python, Go, and now Dart) and many others at the university (C, C++, C#)... ...and Rust is very appealing to me. It's a modern language where the dev tools are straightforward,…
I'm either missing something or words don't mean what they used to...
Some people need to get with the picture and drop those antiquated 2021 practices. Puke!
It's a decent joke, but one of the reasons I only took up Go almost a decade after it got started was that I wanted to invest on a stable language ecosystem that wasn't after the fad of the week (like certain runtimes we all know). I'm actually looking forward to Rust having a few more years under its belt so I can do more than experimentation with it (and yes, I've seen the Oxide stuff, and there is plenty we can ca…
Rust: started 2006, announced 2010, 1.0 2015
The weathering on the two languages seems fairly similar.
In fact it could be argued that Rust is more stable. Golang is talking about a breaking Go2, Rust has a fairly good forward compatibility story and plans.
So Rust is now old enough for people to talk about "Modern" Rust? I'm either missing something or words don't mean what they used to...
There were substantial changes in work flow and tooling each time I dove in and learned the correct way to do things.