
Rustを始めるなら必ずこれを買いたいとずっと思っている。いつになるかはわからないけど😅 rustforjs.dev/ @rustforjsdev

A practical Rust course by @chatsidhartha, especially for JavaScript developers. Preorders open!

Rustを始めるなら必ずこれを買いたいとずっと思っている。いつになるかはわからないけど😅 rustforjs.dev/ @rustforjsdev

Hey you should buy my book: amazon.com/Rust-Atomics-Lock…

Rust’s ownership rules 1. Every value in Rust must have a single owner 2. A value can have any number of immutable references 3. You can only create a single mutable reference to a value 4. If there’s a mutable reference to a value, you cannot have an immutable reference to it

Rust is re-defining Infrastructure engineering. We're seeing the foundations of our tools and services get refactored to it, from CLI to Cloud. Very excited about resources like @rustforjsdev that make it more accessible to everyone!
It’s exciting how much of modern JavaScript tooling is adopting Rust! There’s swc, turbopack, turborepo rewrite (nice work @vercel friends), the new parcel CSS compiler and now the new Tailwind compiler. It’s great to see.

I'm beyond excited to announce that CodeSandbox now has support for the most loved language... @rustlang!! 🦀🦀 Start a new Rust VM in 2 seconds, with: 📦 crates.io support 🦀 @rust_analyzer autocomplete 💡 code actions 💅 auto-formatting codesandbox.io/blog/announci…

It’s exciting how much of modern JavaScript tooling is adopting Rust! There’s swc, turbopack, turborepo rewrite (nice work @vercel friends), the new parcel CSS compiler and now the new Tailwind compiler. It’s great to see.
Whipped up a tiny abstraction to make it easier to run the Tailwind test suite against both our stable engine and the new Rust stuff... Couldn't resist the name 🏒🥅

Getting the finishing touches in on the Building an API server module. We’re going to build an API that runs on @flydotio and persists answers to Postgres for quiz questions for the course. Coming next week!


A lot of folks have wanted to check out a sample lesson in @rustforjsdev Here's the lesson on Lifetimes in Rust! app.rust-for-js.dev/posts/12…

Considering making a lesson in @rustforjsdev public so folks can get a taste of it, which one?

In Rust, it is possible to force-ably allocate values on the heap using the Box type, here is an example of an i32 value allocated on the heap. age is now a pointer to a heap allocated i32.

Rust lets you iterate through something iterable using an Iterator. Here's an example of filtering an array for even numbers. We create an Iterator from our array using into_iter in this case, a version of iter that moves ownership of each value into our closure.

unwrap is fine for code in development or tests but for production, you should probably be calling unwrap_or which lets you set a default for when the value is None instead of panicking!

In Rust, unwrap is a quick and easy way to get a Some value from within an Option when you know for sure that a value is present (because it will panic if the Option is None)

I'm quite happy with how search turned out for @rustforjsdev It's fully accessible, works with Command+K as well and is fast as hell Shipping this to production now

🦀📔 What would you want to see in a book titled "Rust for C and C++ programmers"?