Rust Programming

8150 readers

19 users here now

founded 5 years ago

MODERATORS

nutomic@lemmy.ml

Joe@lemmy.ml

AgreeableLandscape@lemmy.ml

Is it worth it using Rust+Axum for backend instead of Node.js? In which situations would you do so? (lemmy.opensupply.space)

submitted 1 year ago* (last edited 1 year ago) by nyl@lemmy.opensupply.space to c/rust@lemmy.ml

13 comments fedilink hide all child comments

In practical perspectives, I'm mostly concerned about computer resources usage; I have computer resources constraints. So using Rust would benefit on that. But it is for a Web application backend. So, is it worth it having to learn Rust + Tokio + Axum, ... in this specific situation? Also, that this is mostly for initially prototyping an application. Also considering if I add developers in the future, they would most likely not be familiar with Rust, but with more popular frameworks such as Node.

you are viewing a single comment's thread
view the rest of the comments

[–] GissaMittJobb@lemmy.ml 11 points 1 year ago

Consider the constraints and select technology accordingly. You mention being concerned about compute resources, try to elaborate on that.

Are you doing it for ideological purposes? Is your hardware exceptionally constrained? Economical limitations? You will necessarily spend a lot more time compiling when using Rust, so that might eat up any compute savings if the scale of the project is small enough.

If time is a concern at all, then learning a different stack is almost always going to be a losing proposition. Rust is also not the most prototyping-friendly language in my experience - hacking together stuff in Python is almost always going to be faster - but it's by no means impossible.

If for educational purposes, then I recommend Rust, as it is fun and teaches you new ways of thinking about your code.

Finally, the fact that few people know Rust is a real underrated disadvantage you definitely want to consider.

Best of luck with your endeavor.