5 ms·

I wish and I'm sure Rust will get there some day but is there a no-brainer usecase today where it's really important to use Rust, one important enough to overlo

by devsda 2y ago

I wish and I'm sure Rust will get there some day but is there a no-brainer usecase today where it's really important to use Rust, one important enough to overlook the initial learning curve, developer scarcity and evolving ecosystem? If there's a killer open product out there where the primary supported language is Rust(Linux kernel might as well be it someday), or if a big company launches a successful product in Rust then adoption may accelerate. For now its mostly limited to cryptocurrencies, performance critical paths or rewrite of hidden core components but nothing flashy. "Nobody ever gets fired for buying IBM". Unless teams can say the same about their choice of Rust, people are going to be risk averse and prefer using safest choice as long as its good enough.

llm_trw 2y ago
[flagged]
- pdimitar 2y ago
  Nobody is stealing anything, what a weird comment. And the problem with new kernels is how to reuse the huge trove of already-written drivers. Nobody is going to start rewriting everything in any language, be it Rust or any other -- does not matter. That's why the ABI and "please commit to a standard" points are so difficult and thorny in the kernel ecosystem; people want to reuse.
  - llm_trw 2y ago
    Again if it's so great fork the kernel and make it great. People will flock to you if you can manage.
ttfkam 2y ago
Another use case is when you need a systems language for a user-facing app (even if not directly connected to the internet) and would have reached for C++ previously. Memory corruption bugs are no joke. If you've got staff that already knows C++, their ramp up time for Rust will be much shorter compared to typical devs working only in Python, JS, etc.
- pjmlp 2y ago
  Most of that stuff can actually be done in compiled managed languages, and people reach out to C++ because of bias against anything with automatic resource management, even if C++ like features are part of the package.
deleted 2y ago
[deleted]

by devsda 2y ago

llm_trw 2y ago

[flagged]

pdimitar 2y ago
Nobody is stealing anything, what a weird comment. And the problem with new kernels is how to reuse the huge trove of already-written drivers. Nobody is going to start rewriting everything in any language, be it Rust or any other -- does not matter. That's why the ABI and "please commit to a standard" points are so difficult and thorny in the kernel ecosystem; people want to reuse.
- llm_trw 2y ago
  Again if it's so great fork the kernel and make it great. People will flock to you if you can manage.

ttfkam 2y ago

Another use case is when you need a systems language for a user-facing app (even if not directly connected to the internet) and would have reached for C++ previously. Memory corruption bugs are no joke. If you've got staff that already knows C++, their ramp up time for Rust will be much shorter compared to typical devs working only in Python, JS, etc.

pjmlp 2y ago
Most of that stuff can actually be done in compiled managed languages, and people reach out to C++ because of bias against anything with automatic resource management, even if C++ like features are part of the package.

deleted 2y ago

[deleted]