Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Rust is actually more suited to those companies than the general public (small companies and individual programmers) so it makes sense they do push it hard.


Arguably Rust is great for small/single owner companies as well. It saves vast amounts of time in comparison to c/c++


Why would you say that is, or why do you think so?

I would argue Rust is definitely suited towards small companies and individuals for a lot of projects that C/C++ would’ve been used for before, even things like small audio units or plugins


Jonathan Blow puts it as the "cost of experimentation being too high" which I would agree with. Generally, as an individual or small group the limiting factor for you at times becomes time.

Sort of the philosophy where you design by programming instead of whiteboard or clearcut stuff. Less flexible design but more automatic correctness is worth it for big companies because projects involve millions of lines of code and thousands of people over the lifecycle.

It's sort of like writing microservices when you're an one man shop. The correct philosophy is monolith first - until you're doing something useful, don't obsess that much.

If you've got a clear vision of each project, or perhaps it's a larger scale project more similar to those in big tech, then perhaps Rust is best. But those kinds of projects typically don't even need C++/Rust. I use C++ for high performance experimental software.

I would like a C++ replacement also though, maybe through a design like Carbon where it's built above it. You could also then do stuff like making the borrow checker optional and with parts of the program instead, as a sort of finalization refactor. Combining the best of both worlds.


While true, the majority of development doesn't happen in systems languages but generally in garbage collected languages.


Rust has many design features that make it work well for larger teams.


Well that's not saying much. So does TypeScript. Those features that make it suitable for larger teams also make it a solid choice for smaller teams. It's hard to imagine a feature that benefits a large team much more than would benefit a smaller team but I'm open to an argument


The benefits of making illegal states unrepresentable, providing safe abstractions over unsafe boundaries, and high-quality built-in documentation scale quite nonlinearly to large teams is all.


Rust tries to be foolproof.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: