rust-raspberrypi-OS-tutorials VS swc

I am very interested in this tutorial for building an OS for the Raspberry Pi in Rust: https://github.com/rust-embedded/rust-raspberrypi-OS-tutoria...

I'd love to try it out when (if ever) I have the time.

I like rust, low level and embedded hacking so I programmed a simple "kernel", based on this: https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials

So every week, I basically followed along these tutorials. I didn't even made an effort to fully understand the code I was copying, as I just didn't want to waste mental energy on it as I wanted that energy and time wasted on my focus at the time (C++ and JS). I did that for like a year, doing 1-3 tutorials/week from that site. Over the course of it, I got to build web apps, several compilers, several games mostly board games/3d shooters/2d multiplayer games, raytracers, peer to peer apps, building a networking stack, bots, blockchain apps, servers, PGP encryption, E2E encryption apps such as for messaging, built a NES emulator, virtual machines, simulators and graphics programming, etc. I'd say the longest one was learning to build a tiny OS on raspberry pi

Hello everyone, I'm not sure if this is possible, but I'll give it a shot. I have a raspberry PI zero and a linux host pc. I am trying to run stuff on the raspberry on bare metal, no OS below it (using this tutorial https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials/). Now in the tutorial 4 there is a step "flash the kernel onto SD card and insert the SD card into the raspberry". Now, given my lack of SD card adapter (I'm also curious) I wanted to ask if it is possible to deliver this kernel onto the raspberry without the SD card using USB.

I believe it already exists: https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials

Is this just an alternative UI for GitHub but without the files? Am I missing something obvious? I'm confused.

Actual github repo for anyone looking for the files: https://github.com/rust-embedded/rust-raspberrypi-OS-tutoria...

A big part of my work revolves around JavaScript tooling, and as such it's important to keep an eye on the ecosystem and see where things are going. It's no secret that recently lots of projects are native-ying (??) parts of their codebase, or even rewriting them to native languages altogether. Esbuild is one of the first popular and successful examples of this, which was written in Go. Other examples are Rspack and Turbopack, which are both Rust-based alternatives to Webpack, powered by SWC ("Speedy Web Compiler"). There's also Rolldown, a Rust-based alternative to Rollup powered by OXC ("The JavaScript Oxidation Compiler"), but Rollup itself is also native-ying (??) parts of their codebase and recently started using SWC for parts of their codebase. And finally, there are Oxlint (powered by OXC) and Biome as Rust-based alternatives for Eslint and Prettier respectively.

I began by creating a monorepo using turbo with applications and packages. It took me 5 minutes with everything installed and working like a charm! Then I was setting up the backend application, utilizing swc to transpile TypeScript into CommonJS format.

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.