If you're writing Python tools to support OS operations in prod, you need to target the system Python. It's wildly impractical to deploy venvs for more than one or two apps, especially if they're relatively small. Developing in a local venv can help with that targeting, but there's no substitute for doing that directly on the OS you're deploying to.
This is why you DON'T write system tools in Python in the first place. Use a real language that compiles to a native self contained binary that doesn't need dependency installing. Or you use a container. This has been a solved problem for decades. Python users have been trying to drag the entire computing world backwards this whole time because their insistence on using a toy language invented to be the JavaScript of the server, as an actual production grade bare metal system language
Hmm, you mention in the README that it only works in a privileged container. This of course negates the security benefits Wayland supposedly has over X11, so it doesn't seem ideal.
I love Wayland a lot, but as far as I can tell the available remoting solutions still cannot enable a headless LXC container to serve a KDE Plasma Wayland desktop. I spent the last couple days trying to cobble some solution together for it and failed miserably. If you know a way, I would be most grateful :-)
Blogspam is very disingenuous. Phoronix covers a lot of content in the open source world that isn't well tracked elsewhere, and does some of the best and most comprehensive benchmarking of hardware and software you'll find anywhere on the internet.
Zswap is arguably better. It confers most of the benefits of zram swap, plus being able to evict to non-RAM if cache becomes more important or if the situation is dire. The only times I use zram are when all I have to work with for storage is MMC, which is too slow and fragile to be written to unless absolutely necessary.
Forums need to make a comeback. Kids these days not only don't know what they are, but have trouble understanding them when explained. I somehow feel like forums could catch on again if there were a shiny enough platform.
To that end, can anyone recommend any decent forum engines? Discourse's UI rubs me the wrong way, and it would be nice to avoid PHP/MySQL as dependencies in general.
As someone who is sometimes on slow/spotty internet, Discourse's loading dots/circles rub me the wrong way. Like what are they *doing* for all this time while I wait for a page of relatively simple-looking HTML to load? I kept seeing these familiar coloured dots on seemingly disparate sites and it took me a while to realise they were all running Discourse.
I've spent (way too much) a lot of time on forums built using xenoforo, though I'm not sure of what's the stack underneath and what was built-in and what had been added by the operators.
My diesel VW had adblue, and still was affected by deiselgate. The ecu fix took my highway mpg from 35-50 to 18-24, and made the APR tunes incompatible.
reply