Maybe try research instead of reactionary comments.
2) Including homebrew in a Linux distro is a criminal offense normally punished by public flogging.
I remember having great fun in QuickBASIC. And my son enjoys Scratch.
Django code is much more fun to work with than Node, but I can't imagine developing something competitive in it in 2025 to what I'm developing in Node. Node is a pain in the butt, but at the end of the day, competitiveness is about what you deliver to the user, not how much fun you have along the way.
* I think the most fundamental problems are developer-base/libraries and being able to use the same code client-side and server-side.
* Django was also written around the concept of views and templates and similar, rather than client-side web apps, and the structure reflects that.
* While it supports async and web sockets, those aren't as deep in the DNA as for most Node (or even aiohttp) apps.
* Everything I do now is reactive. That's just a better way to work than compiling a page with templates.
I won't even mention mobile. But how you add that is a big difference too.
It's very battery-included, but many of the batteries (e.g. server-side templating language) are 2005-era nickel cadmium rather than 2025-era lithium ion.
I would love to see a modern Node framework as pleasant to work with, thought-out, engineered, documented, supported, designed, etc. as well as Django, but we're nowhere close to there yet.
Plenty of Django businesses making tens of millions. Some in the billions.
I know a solopreneur making around $2m a year and all he uses is Django
What? https://tracker.debian.org/pkg/hyprland https://packages.fedoraproject.org/pkgs/hyprland/hyprland/
>But couldn't for the life of me figure out how to install Arch.
I mean, come on. Sure, Arch is not for everybody, but if you are semi tech savy you could have done the internet searches I did and figured out which distros have hyprland packages. Both Fedora and Debian have them.
Arch is also not much harder to install than debian. Insert the image and go through the steps in the installer, this isn't some magic ritual. https://wiki.archlinux.org/title/Archinstall
I'll even help you. JaKool is the most popular option.
While you're at it, check how many versions the debian package is behind arch/upstream.
It blows my mind how confident people are about knowing something just because they read it somewhere without verifying it themselves.
Vanilla arch is missing so much niceties that take too long to setup.
When your line of thinking there shouldn't be any distros. Just mainline Linux kernel.
The Arch forums rightfully warn against this and do not want users of these distros, since all these distros are inevitably broken in their own weird ways.
There are multiple very reasonable distros. There is absolutely no need to make these forks.