Live data from Hacker News

High-Level Rust: Getting 80% of the Benefits with 20% of the Pain

hamy.xyz

21–30 of 122 posts

Re: High-Level Rust: Getting 80% of the Benefits with 20% of the Pain

#21
Most of the Rust code I've read is arc-mutex-slop.

What this optimizes for is not actually having to deal with the pain in the ass that proper Rust is, but still allowing you to be in the cool kids club writing "blazingly fast software", all while writing what's pretty much Java or C#, but with a terrible non-functional garbage collector instead of a state of the art one.

Re: High-Level Rust: Getting 80% of the Benefits with 20% of the Pain

#22
Isn’t this “high level rust” idea similar to swift?

Everything is ARC. Clones are cheap. But you still have a reasonable sound type system and no garbage collection.

I get it. Tooling on swift is meh the further you are from Apple, so I’m not suggesting it’s better.

But from a language point of view; is it not essentially a high level rust?

Ps. I don’t really know swift. Just asking where/why I’m wrong really.

Re: High-Level Rust: Getting 80% of the Benefits with 20% of the Pain

#23

Most of the Rust code I've read is arc-mutex-slop. What this optimizes for is not actually having to deal with the pain in the ass that proper Rust is, but still allowing you to be in the cool kids club writing "blazingly fast software", all while writing what's pretty much Java or C#, but with a terrible non-functional garbage collector instead of a state of the art one.

> Most of the Rust code I've read is arc-mutex-slop.

Skill issue

Re: High-Level Rust: Getting 80% of the Benefits with 20% of the Pain

#26
post #8
post #6

I agree that the rust community frowns a little too much on the use of Arc/Cloning/Box. If you use swift, everything is ref counted, why subject yourself to so much pain for marginal gain. Tutorials and books should be more open about that, instead of pushing complex lifetime hacks etc., also show the safe and easy ways. The article gives Java a worse devx rank than Go and I can't agree. Java is at least on par with…

Pretty sure by devx they mean something like syntax ergonomics. Because otherwise rust's devx first class (cargo, clippy, crates.io) so kind of a nonstandard definition. I think it's fair to say Java's "syntax ergonomics" are a little below the rest / somewhat manual like rust or C++ by default.

Yeah, but worse than Go?

Re: High-Level Rust: Getting 80% of the Benefits with 20% of the Pain

#27
Java is a fine language and has sufficiently expressive types. It's the most consistently overlooked language and frankly it's completely annoying. Java is a powerhouse. If you can live with a VM, it's an amazing language. The disdain for Java is honestly just weird. The boiler plate is only marginally annoying to write and makes it considerably easier to read. The 'enterprise ecosystem' is definitely bloat, but that's not Java.

Re: High-Level Rust: Getting 80% of the Benefits with 20% of the Pain

#28

Isn’t this “high level rust” idea similar to swift? Everything is ARC. Clones are cheap. But you still have a reasonable sound type system and no garbage collection. I get it. Tooling on swift is meh the further you are from Apple, so I’m not suggesting it’s better. But from a language point of view; is it not essentially a high level rust? Ps. I don’t really know swift. Just asking where/why I’m wrong really.

It's not ARC though. They use fancy threading mechanisms to avoid having to check on every access. Much faster.

Re: High-Level Rust: Getting 80% of the Benefits with 20% of the Pain

#29

Java is a fine language and has sufficiently expressive types. It's the most consistently overlooked language and frankly it's completely annoying. Java is a powerhouse. If you can live with a VM, it's an amazing language. The disdain for Java is honestly just weird. The boiler plate is only marginally annoying to write and makes it considerably easier to read. The 'enterprise ecosystem' is definitely bloat, but that…

1. Java is mentioned in their comparison table. They just don't use it much. 2. There is really no reason to include Java in the search for your preferred language, since Kotlin is strictly better along every relevant axis.

Re: High-Level Rust: Getting 80% of the Benefits with 20% of the Pain

#30

Is this another AI article? What is said about Rust here has been said over and over again, and this brings nothing new to the table. They also always seem to be writing from a place of ignorance. If you're writing "high level Rust" the use of clone or Arc or whatever is negligible. If you're writing an HTTP service, your clone will be so fast it will make literally zero difference in the scope of your IO bound servi…

What triggered me was the proposed Arc as a quick fix. I was highlevel rustin along the learning curve as the article describes until i stumbled uppon dyn-compatible types and object safety.

It is too easy to trap yourself in by sprinkling in Sized and derive(Hash) ontop of your neat little type hierarchy and then realize, that this tight abstraction is tainted and you cant use dyn anymore. As a follow up trigger: This was when i learned derive macros :)

Post reply on HN