cargo-leptos VS swc

> separate-front-target-dir = true

This is now enabled unconditionally and the Cargo.toml option is deprecated since cargo-leptos 0.2.3, it is going to be removed in 0.3

https://github.com/leptos-rs/cargo-leptos/pull/216

https://github.com/leptos-rs/cargo-leptos/issues/217

https://github.com/leptos-rs/cargo-leptos/commit/b0c19a87cff...

Leptos is a SolidJS-like framework with excellent performance. It has a great server-side story as well with server-side rendering & client-side hydration as well as what they call "server functions"; essentially define a function server-side and it can be called client-side without having to deal with http and API design. Also great tooling story with cargo-leptos, leptosfmt (as well as leptos-language-server)

Leptos got it working a couple weeks ago as well: https://github.com/leptos-rs/cargo-leptos

Future opportunities - This one's tougher to speak to since leptos is new on the block. I think it's worth exploring leptos (or sycamore?) just to learn about fine-grained reactivity, and comparing how it works compared to a traditional react model. But to me the ecosystem around leptos is promising, with tools like cargo-letpos, leptosfmt, and more, it seems the community is stepping up to help fill some gaps.

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.