Why JavaScript Devs are Switching to Rust in 2024

In this video, we explore the reasons why JavaScript developers are increasingly drawn to Rust in 2024. Here's how Rust's robust features, including its: unique ownership model, memory management, and type system, offer a refreshing change from JavaScript's dynamic nature.

A lot of JavaScript developers wonder why they should switch to Rust in 2024 so in this video, we will explore some of the biggest challenges and changes if you decide to make the transition.

We also delve into practical steps for JavaScript developers transitioning to Rust, ensuring a smooth and efficient learning experience. Whether you're curious about Rust or planning to make the switch, this video provides valuable insights into Rust's growing influence in the programming world.

Twitter 🐦

TikTok 📱

LINKS

TIMESTAMPS
0:00 Intro
0:17 Rust Background
0:53 Rust Compiled Language
1:15 Memory Management
2:56 Memory References and Borrowing
3:47 Variables and Mutability
5:35 Similarities between JavaScript and Rust
6:06 Types
7:54 Error Handling
8:54 Learning Steps you can Take
10:16 Outro

[warpdotdev]

We are very excited to see what developers will build with Rust in 2024!

Let us know if you'd like to see Rust tutorials! 🦀

[Wielorybkek]

It's not JavaScript devs switching to Rust... It's tool devs switching to Rust.

[scienctv]

actually... we're staying with JavaScript

[okie]

I have heard maybe only one or two isolated cases in the past 3 years of people actually switching from JS to Rust. Most of the time the switch is between frameworks, and the latest trend is switching to Svelte.

[dinosaursnack]

Why would any JS dev working on web applications switch to a language that doesnt target the browser? Rust is an alternative to C or C++, not JS. Downvoted for clickbait title.

[bearziif-s]

amethyst has been inactive for 2 years now. rocket only recently got support after a long time of inactivity. bevy for game development and axum or actix for backend. those are the stable recommended choices.

[romann]

Switch from JavaScript to Rust if you want to get one of those 10 jobs that are available in Rust 😅

[ProjSHiNKiROU]

On fighting the borrow checker: Don't put Rc/RefCell on everything, instead design the memory management of your types to avoid circular references.

[IceFinnland]

I feel like the fact that "Rust does not target your browser but your system" (on 1:08) was a bit easily brushed off as something that would not change anything for people who are used to code in JavaScript. Like JS developers would just go: Ahh my code does not run in the browser any more and it is stuck here on my local machine. Ah well, I guess I will just code for myself from now on or maybe I could offer people to download an executable to run my programs, nobody will ever find that suspicious...

[andrry_armor]

You actually answered a different question for me: why Rust is better than C/C++. Memory controllling is exhausting but Rust makes it more easy and fun. I am already thought about learning go and kotlin, but now I add Rust to the list

[ameer]

It's been two month I've been learning rust as a js dev and I'm having a blast. Currently building an emulator

[johnucci]

Great video! You did have one small mistake though. i32 range is around plus or minus 2 Billion, not million. Once again, great video!

[slr]

Rust is a different class of language to JS they are not interchangeable. Language class determine how it relates to memory and consequently this affects performance. JS is in the same class of language as Python, Perl, and PHP, mid tear languages such as C#, Java, Go deal with memory in a slightly different way. And finally systems languages (Rust, C, , C++, Zig, ) gives you control over more aspects of memory allocation (including where memory is allocated).

[KyleKjorsvik]

Pretty much any language outside of JavaScript will make you hate JavaScript, but it isn't going anywhere.

[eastern_european]

I've breathy read the "Rust the programming language" book and none of the imports/exports or the overall module system worked like it does in JavaScript. (Even compared with older CJS syntax.)
I think that JS devs are not abandoning JS in favor of Rust, it's only those who create tools for the JS ecosystem, so what is really happening is that we are becoming like Python, and it's C-based libraries.

[rohan]

No matter what you do, JavaScript will be around you like a shadow, you can ignore it but you can't remove / replace it

[someverycool]

If the first argument is about memory management, I'm not really sold, since I've never faced these problems with either JavaScript or TypeScript. It seems like memory has been fairly abundant enough with modern challenges I've faced.

I'm just not seeing why any of this would make JavaScript developers make a change.

Sure, if I have some very performance sensitive algorithm or use-case, but why would I be there in the JS in the first place?

[drcphd]

Using Rust for web development is like using nail clippers for your lawn.

[UliTroyo]

For me it's more like: I look at the tools I use most (WezTerm, Nushell, Helix, Broot, ripgrep) and they're all built with Rust. It just makes sense to use it.

[a-yon_n]

It's not that js devs are moving to rust, it’s js tools are moving to rust. There is a huge difference, which means, no matter how good rust promises, it needs js to live.