rust-raspberrypi-OS-tutorials VS delta

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

Thanks for the difftastic & zoxide tips.

However, I've been using this git pager/difftool: https://github.com/dandavison/delta

While it's not structural like difft, it does produce more readable output for me (at least when scrolling fast through git log -p /scanning quickly

View on GitHub

I'm currently waiting on the integration between Delta and Difftastic:

https://github.com/dandavison/delta/issues/535

Difftastic now has JSON output, whic should make it much easier to build this.

I'm surely in the minority here. I've been using Emacs for almost a decade now, but I just can't get into the Magit workflow. I've tried several times, but always end up going back to Git on the command line. I have dozens of aliases, shell integrations, a nice diff viewer[1], etc., and interacting with Git has become muscle memory. I can commit, cherry-pick, rebase, bisect, fix conflicts, etc., in a fraction of the time it would take me to navigate Magit's UI. I'm sure with enough practice, a Magit user could do this more quickly and efficiently, but honestly, with some custom-built porcelain, Git's UI is not so bad. Though this could very well be Stockholm syndrome after using it for such a long time...

For whatever reason, Magit's opinionated workflows never clicked with me. A part of it is the concern that it will do something weird to my repo that I'll then have to waste more time undoing manually. I usually don't trust sugary wrappers around tools. And another is the fact I don't use Emacs on all machines, and setting up Git on a remote system is just a matter of copying over my config and some shell integrations.

Also, on a more personal note, I find the cultish fanboyism whenever Magit is brought up slightly offputting. Does anyone have anything bad to say about it? No software can realistically be this infallible. :)

[1]: https://github.com/dandavison/delta

For looking at diffs I still prefer the command line though, and use delta to view diffs between commits or branches.