Baby Mammoth - Another Day at the Orifice
Baby Mammoth - Another Day at the Orifice
Dude I mean in this in the most genuine, kind way: a significant aspect of being a successful programmer is using the tools in your environment. If you can’t do something without bringing in your Tool of Choice you’re artificially limiting yourself.
If your environment does not have a specific tool or functionality that you would prefer, you work around it. OpenWrt is an immensely capable OS and it manages to perform complex network operations within its (admittedly) constrained environment.
In this case you’re myopically focused on not even a specific language, but the language agnostic feature of regex capture groups. You should be asking yourself if there’s any other way to accomplish your goal without this (spoiler: there are probably dozens of alternatives)
Lua is 31 years old and has been included in OpenWrt by default for 15 years.
If it’s OpenWrt then use Lua. You probably could have written a solution in the time it took you to come whine about BusyBox.
I don’t know if this is still the case, but IIRC browsers (chrome and Firefox) have their own sandboxing which is quite effective, but their efficacy is hindered by flatpak.
Early Knoppix live CDs have a special place in my heart
I’ve used silverblue on my gaming rig for over three years now. It has been a completely uneventful experience, so I really like it.
The only pain point I have is that compiling kernel modules is an utter disaster and it’s ridiculous that there is not a seamless mechanism for this yet. Every kernel update (and there are tons) requires me to rebuild my third party modules, but you need to do it in a toolbox and the kernel headers version must match the running kernel version, which is actually more annoying than it sounds.
C++ is way ahead of C in the same way that a metastasized cancer is way ahead of a benign tumor
Was this written by AI?
Linux has dominated the router firmware market for a loooong time. Nearly all vendor firmware for consumer routers is Linux based.
Nice
Reminder to read the official git book. It’s free and it’s useful. My dudes, stop pretending to understand your tools and actually learn them.
This is amazing
deleted by creator
Our current understanding having spoken to systemd developers is that we should be able to find a path that brings us much closer to upstream, if not entirely.
The only way the systemd developers will allow musl support upstream is if musl supports the glibc-isms that systemd uses.
They have been extremely clear that they will not carry patches for other libcs.
I find GNOME’s “must be perfect” approach to accepting new code counterintuitive.
One of the largest benefits of having a clean architecture is increased velocity and extensibility. What’s the point in nitpicking over perfection when it takes literally years to merge a feature, arguably one considered basic and essential by today’s standards?
KDE is on the other side of this pendulum, integrating everything and resulting in a disjointed, buggy disaster.
Where’s the middle way? It used to be XFCE. What is it now?
This is awesome work, I’m happy to see systemd on musl getting more attention. Poor Khem was doing it all by himself for years.