Good job. I kinda feel like it needs a bit more textury look. And a ton of gradients.

Just a small note, scanning is handled by SANE. So you have to look for that is some form, when troubleshooting.

I can only recommend. Easy to use and error messages are actually readable by a human being. AFAIK, only problem is running external commands (some packages use them).

I partially agree. I recently started to heavily use typst for any typesetting where I have enough time to make a template. But as far as I know, typst does not support all the little things LaTeX can do.

For instance hyperref can highlight links so they look different on paper and different in the viewer. Last time I checked, typst backend does not support using those layers.

I also have mixed opinions on math syntax. It is great, but current parser implementation really wants you to put in some spaces that make the typing little awkward.

Great plus is proper Unicode support. I remember having trouble citing chinese document names in bibliography, because half of the names wouldn't use the correct font.

Overall, it's great, but I don't consider it to be direct replacement.

The switch or dual boot is up to you. I can lay out some general steps in case you want to have an overview. Please do not be scared off by it. Depending on the distro, most things work out of the box or with very little effort.

1. familiarize
   • look up some distros, I personally like to go Arch-based, but feel free to use whatever seems good and popular enough (please no Ubuntu)
   • try virtual machine and then live ISO
2. verify compatibility
   • this one is a bit more work, basically try all functionality in the live ISO, or at least things like display, mouse, keyboard, touchpad, Wi-Fi, storage
3. install
   • you probably won't need to look into this super deep, default installers handle this pretty well
   • formatting and partitioning (look into ArchWiki guide, you probably don't need swap partition)
   • if you are going to be reinstalling look into using efibootmgr to possibly clear up old and fix existing boot entries (i had to enable boot flag after setting up dualboot, because macOS installer overwrote the previous settings, thanks Apple :-) )
4. configure missing/not working OS stuff
   • look for missing drivers and system management software for either your specific hardware or some more general ones
   • best sources are wikis like ArchWiki (even if you don't use Arch), forums and some software search sites like AlternativeTo
   • in some cases the software does not meet the requirements for a wiki page to be up (Xlibre being notable example - feel free to look up the whole story)
   • you may have to put some time into getting GPU fully working, since nvidia has several driver options depending on the GPU
   • I personally had to fix USB autosuspend config, only look into it if devices plugged in after boot are not being detected
5. use
   • installs and updates are done using package manager (windows has winget, btw)
   • for windows games use Wine or rather some of its forks
   • most people here already shared their recommendations for this part

edited

The fact that there is this section in the README even though all the code has docstrings and you can generate the docs is certainly interesting.

Brother distributes its own drivers, but there are some alternatives like brlaser. Both mentioned drivers work great on linux in my experience.

I think a bit of rounding can look good. But I feel most of the designs these days are overdoing it.

Man, I really can't wait to put border-radius: 100% on my entire desktop for proper roundnessmaxxing. And add in liquid glass and blur to every sigle letter, button, window, icon, heck even my word processor, text editor and images displayed by my image viewer, ...

Maybe luakit, If you want gui. Dillo, if you don't care about the looks. And w3m for terminal.