rustlings-solutions-5 VS swc

https://doc.rust-lang.org/book/ https://github.com/rust-lang/rustlings https://doc.rust-lang.org/rust-by-example/

i think you've found what i'm looking for! https://github.com/rust-lang/rustlings

I would recommend rustlings as a way to get used to semantics. It starts from absolute basics but it gave me a more intuitive understanding of the language.

go along with Rustlings https://github.com/rust-lang/rustlings

rustlings — Small exercises to get you used to reading & writing Rust code!

I had finished this Udemy course, which was a bit too fast towards the end but still enjoyable, I read THE BOOK and done the Rustlings (here are my old solutions and here the new ones).

You will get used to it when you write more Rust code. Read the book, implement some exercises and watch some tutorial YT videos, everything will make sense eventually.

Check out rustlings. Simple exercises with writing rust code, introducing new concepts along the way.

There's an official "book" that you can look up online. It goes through Rust step by step, like a tutorial. Alternatively there's the rustling's course where you learn Rust by doing small exercises. I have only ever looked at the book, which is fantastic. But if you know a bit of C and some sort of class-system like in OOP or Haskell's typeclasses you can just look up the syntax when you need to, it is really easy. Also, the compiler warnings/errors usually tell you what you need to do in order to fix your error (especially for simple stuff in the beginning) so often you don't even need to google the issue.

Rustlings might be useful to you: https://github.com/rust-lang/rustlings

First, we switched the default compiler for new projects from Babel to SWC (Speedy Web Compiler). SWC is dramatically faster than Babel and requires zero configuration. We’ll continue to support Babel in any project currently using it.

SWC

As the reference explains “**SWC** (Speedy Web Compiler) is an extensible Rust-based platform that can be used for both compilation and bundling. Using SWC with Nest CLI is a great and simple way to significantly speed up your development process.”

This is specifically about breaking the myth that performing expensive self-contained operations (e.g, parsing GraphQL) in a native extension (C, Rust, etc.) is always faster than the interpreted language.

The JS ecosystem has the same problem, people think rewriting everything in Rust will be a magic fix. In practice, there's always the problem highlighted in the post (transitioning is expensive, causes optimization bailouts), as well as the cost of actually getting the results back into Node-land. This is why SWC abandoned the JS API for writing plugins - constantly bouncing back and forth while traversing AST nodes was even slower than Babel (e.g https://github.com/swc-project/swc/issues/1392#issuecomment-...)

Why Speedy Web Compiler ?

FTA is a TypeScript static analysis tool built on the speedy foundations of swc. FTA is fast; capable of analyzing more than 150 files per second on typical hardware, it offers a powerful addition to your code quality toolkit.

Very cool! I'm curious, is this intended for dev tooling?

For example, I could see this (or something similar) being useful as the engine for a typescript language server that would be faster than the standard one

But if it's not aimed at 1:1 with tsc, would it be intended more for something like swc[1]?

Or what would you expect people to use this for, besides just being a cool project to learn from?

[1] https://github.com/swc-project/swc

This is... good news, but I still cannot fathom using the default Typescript compiler for regular development. Seriously, leave the type-checking to your IDE and CICD chain, and switch to using tsx (https://www.npmjs.com/package/tsx) or swc (https://swc.rs/) and you will _immediately_ notice the difference in speed and productivity.