[lakomen]

I had to laugh at the "great developer experience". Meaningless error messages, unreadable syntaxes, forced structures, no explanation why the solution to certain errors is importing some lib.

You write backend code as of you were writing frontend code, which is not enjoyable. You always have to think about who owns what.

And the whole crate terminology is just stupid. What am I, a dock worker or software designer?

No, to each their own but Rust does not have a great developer experience.

Compile times are long.

What do you gain in performance compared to Go? Not a while lot, and you pay with wasted time aka increased development time and more complicated thought process.

It's not for me, and when this blog says great dx, that means it's a propaganda post. In fact the whole article reads like it's trying to convince someone do something they don't want to.

[roarcher]

> And the whole crate terminology is just stupid. What am I, a dock worker or software designer?

Of all the reasons to complain about a programming language, the package manager not being elitist enough is certainly an original one.

[qweqwe14]

> Meaningless error messages, unreadable syntaxes, forced structures, no explanation why the solution to certain errors is importing some lib.

The compiler has pretty good error messages, `rustc --explain` exists, "unreadable syntax" is a common complaint from people that expect everything to be C-like or Python (or are just trolling), "forced structures" is explained by Rust being a statically typed programming language.

> You write backend code as of you were writing frontend code, which is not enjoyable.

No idea what's this about.

> You always have to think about who owns what.

If your code is well-structured this is a non-issue. The types of people that complain about ownership are the ones that write messy code with chaotic inter-dependencies and unclear semantics.

And besides, you have to do that anyway in e.g. C++, only it doesn't enforce it, which leads to programmer error, which is worse. Or you can use reference counting if you have skill issue.

> Compile times are long.

Compared to what? They aren't much longer when comparing apples to apples: C++ with static analysis tools and Valgrind will have pretty much the same compile times. Again, a bold general statement that doesn't really say much.

> What do you gain in performance compared to Go? Not a while lot, and you pay with wasted time aka increased development time and more complicated thought process.

Performance in what? For non compute-intensive tasks you can obviously pick any language you are comfortable with. Obviously there's no point using C++ to serve a static site when a simple Python server will do. In benchmarks, Rust just murders Go in performance, so you are objectively wrong if you are talking about raw performance.

> that means it's a propaganda post

Based on your wacky arguments, I'd say that your comment is in fact propaganda.

[golergka]

> What am I, a dock worker or software designer?

You really must hate this thing we use instead of VMs nowadays.