Hacker News new | ask | show | jobs
by uecker 427 days ago
I think we will get the same safety benefits of Rust in a version of C relatively soon.
1 comments
koakuma-chan 427 days ago
Borrow checker is not the only feature that makes Rust great though.
link
uecker 427 days ago
Yes, it also has many aspects I do not like about it. Let's not pretend everybody shares your enthusiasm for it.
link
koakuma-chan 427 days ago
What aspects do you not like about Rust?
link
uecker 427 days ago
Too much complexity, long build times, monomorphization, lack of stability / no standard, poor portability, supply chain issues, no dynamic linking, no proper standard, not enough different implementations, etc. It is a nice language though, but I do not prefer it over C.
link
koakuma-chan 427 days ago
> long build times, monomorphization

Monomorphization is what causes long build times, but it brings better performance than dynamic dispatch.

> lack of stability

There was another comment which also never elaborated on how Rust is not stable.

> supply chain issues

Not a language issue, you choose your dependencies.

> no proper standard, not enough different implementations

Is that a practical problem?

> no dynamic linking

There is.

link
uecker 427 days ago
If your like Rust, this is fine, but I will stay with C. I find it much better for my purposes.
link
whytevuhuni 426 days ago
> > no dynamic linking

> There is.

Eh, I'm a Rust fan, and I hate the dynamic linking situation too.

I genuinely cannot see how Rust would be able to scale to something usable for all system applications the way it is now. Is every graphical application supposed to duplicate and statically link the entire set of GNOME/GTK or KDE/Qt libraries it needs? The system would become ginormous.

The only shared library support we have now is either using the C ABI, which would make for a horrible way to use Rust dependencies, or by pinning an exact version of the Rust compiler, which makes developing for the system almost impossible.

Hopefully we'll get something with #[export] [1] and extern "crabi" [2], but until then Rust won't be able to replace many things C and C++ are used for.

[1] https://github.com/rust-lang/rfcs/pull/3435

[2] https://github.com/rust-lang/rfcs/pull/3470

link