91–100 of 520 posts
Good news they adopted Rust as Tier-1 language. I hope their Weather app stop consuming more than 1GB RAM https://www.notebookcheck.net/Windows-11-s-built-in-Weather-...
Earlier quoted context omitted.
Honestly, the only domains that I think rust isn't suitable for are: * rapid-prototyping, where javascript and python are still top-tier * adding scriptability to existing programs, where lua and scheme (and python) are popular * Server-side API implementation (rust is usable here, but I think Go fits the slot better)
Rapid prototyping is almost a meme at this point. If you are hand rolling code old school, you will waste more time shoehorning JavaScript and python semantics into rust code and end up with worse quality that takes more time rather than writing it from rust. People did this a lot when rust was not as popular but there are plenty of very good rust programmers now who understand the language and can make programs that…
> People did this a lot when rust was not as popular but there are plenty of very good rust programmers now who understand the language and can make programs that are significantly more performance for a marginal development cost.
Why isn't the game industry moving to it then? Bc it just cannot compete at volubility with C++, among other things. Yes, you can have skilled people, but the borrow checker is still there and that is an anti-change-me-fast fact of life. I think things like sending batches of info to the GPU in casted ways, alignment, etc. all go against safety naturally but this is fundamentally what needs to be done anyway when transfering data to the GPU, so adding a layer of safety for the sake of doing it to notice that your data-oriented pipeline has to suddenly change its shape would mean repeating work...
Namely, Rust is just not good at this. Rust is good if you can replicate a safe layer that is very reusable every time (when interacting with unsafe) or when you do not need unsafe at all or hardly, where you can take advantage of its safety fully.
Also, there are certain very tweaked data structures such as Boost.MultiIndex or linked lists with intrusive hooks and others that are not easy at all in Rust and they do have value in some situations. I had some of this in some telecommunication systems before.
Earlier quoted context omitted.
Honestly, the only domains that I think rust isn't suitable for are: * rapid-prototyping, where javascript and python are still top-tier * adding scriptability to existing programs, where lua and scheme (and python) are popular * Server-side API implementation (rust is usable here, but I think Go fits the slot better)
Rust is great for rapid protoyping, IMO. Or, at least the subset of rapid prototyping that involves massive rewrites to try out different approaches. Rust has a saying "if it compiles, it works", the compiler really ensures that you don't miss something when doing that rewrite.
If you have to iterate a lot the shape of your code... no, it is not any good at this...
Good news they adopted Rust as Tier-1 language. I hope their Weather app stop consuming more than 1GB RAM https://www.notebookcheck.net/Windows-11-s-built-in-Weather-...
Whether vibecoded Rust will be better than whatever they are doing now remains to be seen.
Maybe this has changed since I wrote Rust, but that was a classic beginner fix. Just throw memory at it.
Earlier quoted context omitted.
Honestly, the only domains that I think rust isn't suitable for are: * rapid-prototyping, where javascript and python are still top-tier * adding scriptability to existing programs, where lua and scheme (and python) are popular * Server-side API implementation (rust is usable here, but I think Go fits the slot better)
GPU programming?
Earlier quoted context omitted.
I like Rust a lot but I'm not sure it would come very high up my list for web applications.
Axum and Actix are phenomenal web frameworks. The type system and error handling ergonomics make it easier to write defect-free code than, say, Go or Java. Simple servers are request scoped and mostly feature linear request handling, so you're writing simple vanilla Rust without the complex pointer semantics that you would use for systems programming. The async pieces aren't difficult either. Serde-annotated structs…
Compared to what? I see ASP.NET Core and Quarkus very competitive. The virtual threads in Java are great, paired with structured concurrency IMHO.
If I have to go microservice or API, I would choose FastAPI for fastest delivery and if I have to rewrite, Go, unless it is massive scale and scaling horizontally becomes a headache I would not consider Rust/C++ for this.
All the backend, etc. for the company I have been working for is C++ for the fast parts but all tools around are Python (with NiceGUI and Flask mostly).
I think the combination is quite powerful, btw.
Earlier quoted context omitted.
Whether vibecoded Rust will be better than whatever they are doing now remains to be seen.
The question in terms of memory is, will vibe coded rust get around ownership issues by .clone()-ing everything. Maybe this has changed since I wrote Rust, but that was a classic beginner fix. Just throw memory at it.