rust-raspberrypi-OS-tutorials VS quiche

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...

The title of this post puts emphasis on "written in C", making me wonder when this would ever be a desirable feature, given that more secure implementations are available, and can be integrated into old C projects just as easily.

No need to rewrite everything from the ground up: https://github.com/cloudflare/quiche#curl

The issue is dead silent too!

https://github.com/cloudflare/quiche/issues/1115

Even though Oxy is a proprietary project, we try to give back some love to the open-source community without which the project wouldn’t be possible by open-sourcing some of the building blocks such as https://github.com/cloudflare/boring and https://github.com/cloudflare/quiche.

They’ve been on the Rust train since at least 2019. Just look at projects like quiche, wrangler, and boringtun

It's more like Cloudflare forked nginx a long time ago, and is meanwhile in the very slow (like, decade-long) process of replacing it entirely.

The Cloudflare Workers Runtime, for instance, is built directly around V8; it does not use nginx or any other existing web server stack. Many new features of Cloudflare are in turn built on Workers, and much of the old stack build on nginx is gradually being migrated to Workers. https://workers.dev https://github.com/cloudflare/workerd

In another part of the stack, there is Pingora, another built-from-scratch web server focused on high-performance proxying and caching: https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...

Even when using nginx, Cloudflare has rewritten or added big chunks of code, such as implementing HTTP/3: https://github.com/cloudflare/quiche And of course there is a ton of business logic written in Lua on top of that nginx base.

Though arguably, Cloudflare's biggest piece of magic is the layer 3 network. It's so magical that people don't even think about it, it just works. Seamlessly balancing traffic across hundreds of locations without even varying IP addresses is, well, not easy.

I could go on... automatic SSL provisioning? DDoS protection? etc. These aren't nginx features.

So while Cloudflare may have gotten started being more-or-less nginx-as-a-service I don't think you can really call it that anymore.

(I'm the tech lead for Cloudflare Workers.)

Ask Cloudflare why they use HTTP/3 and QUIC https://github.com/cloudflare/quiche.

Cloudflare has used rust for multiple projects in the past such as their QUIC/HTTP3 implementation Quiche and a WireGuard implementation BoringTun.