51–60 of 294 posts
Rust is a great choice for startups because most startups fold and so will not need to try to find people who know how to maintain it.
Earlier quoted context omitted.
I would argue that Rust is a great choice for startups exactly because you can find people who will either take a pay cut or work in a hectic environment, just so they can use Rust. Rust has been on top of everyone's "want to learn" list for half a decade, and it feels quite mature.
I'm surprised to see multiple people mentioning pay cuts. In the Stackoverflow Annual Developer survey[1] I see Rust developers consistently being among the highest paid in the industry. [1] https://insights.stackoverflow.com/survey/2021#top-paying-te... edit : adding link to all previous years https://insights.stackoverflow.com/survey
I'm mentioning pay cuts because one of the side-effects of joining a startup is that they can be tight on money and will offer early employees shares instead.
I work for a startup and am coding Rust and my salary went up by taking this job.
So I'm only saying this as a general thing; I'm sure a lot of startups where Rust makes a difference (I'm sure a lot of startups would be just as well off with Python), they can probably afford a competitive wage. :-)
Rust is a great choice for startups because most startups fold and so will not need to try to find people who know how to maintain it.
Earlier quoted context omitted.
I would argue that Rust is a great choice for startups exactly because you can find people who will either take a pay cut or work in a hectic environment, just so they can use Rust. Rust has been on top of everyone's "want to learn" list for half a decade, and it feels quite mature.
Definitely I would not take a pay cut for rust, also for any technology, it’s about solving problems and working on interesting things not really about a language. I’ve also been learning rust in my spare time, and am more and more realising that I spend time solving rust’s problems more than solving the problems of the side project I started
I have only experienced the opposite: That Rust jobs pay well. Also for startups.
Rust is a great choice for startups because most startups fold and so will not need to try to find people who know how to maintain it.
I recently was thinking about how smart/not-smart would it be to become a full-on 'Rust developer'. So I thought, OK, what happens if two decades from now I'm a grey-beard Rust programmer, and the only jobs I can find are maintaining some legacy Rust code... And then it struck me, I'd be completely fine with it. As in, if there's a language in which dealing with legacy code doesn't seem daunting, then that's Rust. Be…
Rust is a great choice for startups because most startups fold and so will not need to try to find people who know how to maintain it.
Maintenance is where Rust really shines and makes up for it's initial learning curve and slightly slower writing speed. In terms of hiring I can't imagine it being a problem either. There are lots of developers who would jump at the chance to work with Rust, and comparatively few Rust jobs (especially ones that don't involve working with cryptocurrency).
In my post notice that aside from my personal background with programming I didn't go into detail about memory safety, which seems to be what many are debating. Frankly, it's not even one of my top reasons for praising the language. If I had to pick three these are what I'd choose:
1. Strong features for describing real-world issues in software. Here I'm talking about things like tagged unions (enums). They let you describe so much very cleanly. Use a match expression on it and you can be sure you've handled it pretty well. These lead into the stdlib's Result and Option types which extend what I said further.
2. Excellent performance without any fancy language stuff like annotating lifetimes. Using the Iterator trait you can chain up a really nice operation FP-style and get ridiculous performance. It takes fewer lines than idiomatic Python.
3. Excellent tooling. Cargo is easily the best package manager I've used (yet, someone show me better!). When doing async work the tracing crate is great, it automatically handles all the entry and exit points of the state machine that gets generated. You can also use tools like tokio-console on it, or export via opentelemetry.
What does Rust offer over modern C++ with smart pointers and RAII?
Earlier quoted context omitted.
Maintenance is where Rust really shines and makes up for it's initial learning curve and slightly slower writing speed. In terms of hiring I can't imagine it being a problem either. There are lots of developers who would jump at the chance to work with Rust, and comparatively few Rust jobs (especially ones that don't involve working with cryptocurrency).
There are lots of people curious about coding Rust in production, and most of them consider themselves competent to write it. But that is not what you look for when hiring. Or, it shouldn't be.
For an analogy, I wouldn't hire a pilot that isn't interested in other planes than what's on their license. What if I want to operate some new models?
Unless I'm looking for someone for a truly specialised role, I would avoid people that stick to only one thing for their entire careers.
>(...) despite my experience and best intentions, I was in fact making mistakes with C. Subtle leaks, use-after-free,(...) Rust made it very clear that I was not the programmer I thought I was. This really resonated with me. I feel a lot more confident writing code in Rust than say in C or Java. However, in my opinion, it also comes with a downside: These days, whenever I use a 'more forgiving' programming language I…
I understand the comparison with C (the memory management) but I wonder how do you compare Rust to Java? What is it that makes you feel more confident in Rust compared to Java?