Why Rust is a great choice for startups
dailyedit.com
Why Rust is a great choice for startups
1–10 of 294 posts
Re: Why Rust is a great choice for startups
#2Rust 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.
Re: Why Rust is a great choice for startups
#3Rust 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.
If you build a startup around bad ideas realized in crappy languages, than it's a great recipe for a disaster.
If you have a good idea and you hire seasoned developers who can realize this idea you are at least on the good path.
Re: Why Rust is a great choice for startups
#4Rust 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.
If you build a startup around bad ideas realized in crappy languages, than it's a great recipe for a disaster. If you have a good idea and you hire seasoned developers who can realize this idea you are at least on the good path.
Necessary, but not sufficient. Almost all the startups with bad implementations will fold. Almost all the startups with good implementations will fold.
Re: Why Rust is a great choice for startups
#5>(...) 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 find myself being much more paranoid of the code that I write. Even after double checking everything I still miss the memory guarantees that Rust brings, and end up spending a lot of time making sure things are behaving the way they should.
Re: Why Rust is a great choice for startups
#6>(...) 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…
Do you pine for the nice days of C/C++, when men were men and spend hours on debugging segmentation faults?
Re: Why Rust is a great choice for startups
#7Rust 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.
If you build a startup around bad ideas realized in crappy languages, than it's a great recipe for a disaster. If you have a good idea and you hire seasoned developers who can realize this idea you are at least on the good path.
Zuckerberg something...
Re: Why Rust is a great choice for startups
#8Earlier quoted context omitted.
If you build a startup around bad ideas realized in crappy languages, than it's a great recipe for a disaster. If you have a good idea and you hire seasoned developers who can realize this idea you are at least on the good path.
Necessary, but not sufficient. Almost all the startups with bad implementations will fold. Almost all the startups with good implementations will fold.
I worked for a company that used some crappy 2000s 4GL nocode tool to get started. Didn’t hurt them financially at all.
Re: Why Rust is a great choice for startups
#9Rust 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 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.
Re: Why Rust is a great choice for startups
#10>(...) 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 still find this type of comment odd (although I do also recognise that it's very common).
I write a lot of code in C++. And I'm definitely no fan of it, so I'm not here to defend it! And I write a lot of bugs in that code. But very few of them are segfaults. With smart pointers and some common sense, they're just not that big of a concern. Yes, they do happen, but it's far a minority of the bugs. Maybe everyone just has better tests than me? (shrug)
I like the look of Rust, though I haven't yet got to use it professionally. I actually think it would be a perfectly good language without all the lifetime stuff, with lots of improvements over C++ (destructive move for a start). It would probably be good enough for most purposes, and the improved uptake would result in fewer bugs overall than the current situation.
It's academic really since that's obviously not where we are. But, like I say, I don't think memory errors are that problematic in C++ in practice (unless you're writing security sensitive code where even an occasional one can cause big problems).