this post was submitted on 15 Sep 2023
30 points (75.9% liked)

Rust

5398 readers
51 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
30
Should I Rust or should I Go? (kerkour.com)
submitted 9 months ago by [email protected] to c/[email protected]
21 comments fedilink hide all child comments
 

I think some raised points are relevant...

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 15 points 9 months ago (1 children)

I maintain a long-term Rust + Node.js project, and the Node side is the painful one.

Node makes backwards-incompatible changes, and doesn’t have anything like the editions to keep old packages working. I can end up with some dependencies working only up to Node vX, and some other deps needing at least Node v(X+1).

[–] [email protected] 6 points 9 months ago

That's an issue with almost the entire js ecosystem. I'm part of a project that has rather high security standards, so we have to keep everything updated. The Java side is almost trivial, update some version number, let the tests run and you're fine. The js side is a constant battle against incompatibilities, weird changes for no reason and simply tons of vulnerabilities.