News for hackers. Stuff that matters.
Re:Mapping my walks with OSRM and Rust by amelius on Saturday January 22, 2022 @05:32AM (#30035465)
> There's nothing inherent about Rust that makes it unsuitable for high level projects.

I don't agree. A garbage collector is very useful for high level projects. The problem with Rust is that you might run out of options once your project grows bigger. So in fact, choosing Rust is limiting your options. Garbage collected closures are very powerful, and missing in Rust. It's probably one of the reasons why Rust has no stable GUI yet.

Re:Mapping my walks with OSRM and Rust by jeffparsons on Saturday January 22, 2022 @05:45AM (#30035536)
I think this may be more of a problem for people who are, because of the language(s) they are coming from, used to throwing everything at the garbage collector to sort out.

I've been writing Rust for years now, and the number of times I think "jeez, I wish I had a garbage collector right now" are so very few and far between that I can't come up with a single example right now.

That is to say, I really think it has more to do with what you're familiar with.

> It's probably one of the reasons why Rust has no stable GUI yet.

I don't think there's much to this hypothesis. It's more likely that for people who really want something right now, there are plenty of bindings to GTK etc. that work quite well. People who are interested in a novel, idiomatic Rust GUI framework tend to be more interested in thoroughly exploring lots of different ideas than committing to one of them. That is to say, there's not actually any great urgency to slap together something that works that you could call "a Rust GUI", because in practice plenty of those options already exist!

Re:Mapping my walks with OSRM and Rust by tlamponi on Saturday January 22, 2022 @06:02AM (#30035620)
> A garbage collector is very useful for high level projects.

Rust solves most (or even more) of the problems GC does already with the borrow checker, I'd argue that one does not want to spent time thinking about stutters/latency spikes due to micro pauses or stop-the-world events from a GC in a very complex code base — granted GC's got a lot better, but there are still issues out there.

At work, we may not be the big, huge enterprise project, but Proxmox Backup Server is not small either and packs a lot of features (REST API, content addressable storage layer, backup management, system (network, time, update) management, ...) together spanning from low to high level. So, I'd figure it has at least a medium complexity. The thought that a GC would help us never entered my mind, nor did any of our devs mention it — most of them explicitly expressed at some time that they are glad there's no GC.

Besides that, Rust makes refactoring a bliss, which is a major plus point in big, complex projects with multiple teams working on a (partially) shared code base.

> It's probably one of the reasons why Rust has no stable GUI yet.

I think that is rather a reason of why a rust GUI could be superior to use, even from another language (GC or not) — I mean, it allows memory management without GC (slightly better performance, faster memory reclaim and no micro-pauses or the like) but also avoids lots of memory (mis)management bug classes. But yes, you're right in that there's no good plain-rust GUI framework with a stability guarantee, druid may be pretty close and has some project showing that it can work OK and look good already, e.g.:

https://github.com/jpochyla/psst

https://github.com/lapce/lapce

Re:Mapping my walks with OSRM and Rust by detaro on Saturday January 22, 2022 @05:43AM (#30035523)
Lots of very large GUI applications and libraries are written in C++, and do just fine without language-level GC. And Rust gives you tools to manage a lot of the issues you have there.
Re:Mapping my walks with OSRM and Rust by pjmlp on Saturday January 22, 2022 @07:14AM (#30036003)
There is a reason why many of such frameworks have been moving into a managed layer, including Qt.