![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
All public companies are, it’s just what Boeing makes things that fall out of the sky if they mess up, so it’s more obvious.
All public companies are, it’s just what Boeing makes things that fall out of the sky if they mess up, so it’s more obvious.
Just have NAS A send a rocket with the data to NAS B.
I remember the clusterfuck that existed before systemd, so I love systemd.
By having the stupid idea of existing next to Russia (or a similar country).
If this was done by multiple people, I’m sure the person that designed this delivery mechanism is really annoyed with the person that made the sloppy payload, since that made it all get detected right away.
Then they’ll just identify you by the sound of the printer being audible from down the street.
Seems to me that a lot of the world’s problems start with “well, the managers think…” They all seem extremely bad at the whole managing thing, good thing we don’t overpay them or anything like that.
TIL there are Linux people that don’t use OpenWRT. I always assumed everyone in the Linux community used it. It’s great.
Works great with mt7621 based routers if anyone ends up looking for something compatible.
Linux and a windows virtual machine with a dedicated nvme hard drive and GPU using PCI pass-through. Windows is boxed in but easily accessed when you need it, and the performance is 95% of native, or more. And because of the dedicated hard drive, you can still dual-boot it like normal if you want.
Also, I recommend installing windows 10 enterprise in the VM, minimal bloat.
I use gnome for the most part. I have been checking out kde recently to see how the newer versions stack up (gave up on it during the 4.0 days). As you mention kde supports dpms changes on wayland because they have their own protocol extension for that.
That’s actually my biggest gripe with wayland - the huge amount of fragmentation it has caused. I’m pretty confident that almost all the missing features I talked about are possible on one or two of the compositors, but not all of them. And definitely not on the one I use. I’m sure once some pragmatism takes hold that all the issues will be ironed out, but my plan for now is to stick to X11 until that happens.
For me it’s a million little details that just don’t work. Stuff like positioning windows, removing decorations from a window, remapping buttons on a trackball, setting a graphics output to tvrgb, disabling a display via ssh and enabling it again, etc.
It’s not just about hardware compatibility. It has to be compatible with existing workflows, and it’s currently very limiting.
I don’t work for Apple, but I am an electronics engineer. Just don’t be surprised when your simpler devices start failing.
To be fair though, they just need to make everything USB-C anyhow.
Careful what you wish for. Putting advanced electronics into very simple devices will just make them fail a lot faster.
Some old device just needed 12V over a barrel jack to run some motor or light and charge the battery and it lasted a decade - only failed because the battery got old. New one now needs a state of the art power delivery chip to negotiate the right voltage and current, and all over a very fine pitch connector that will fail if you look at it wrong. Not looking good on the durability front at all.
set -euo pipefail
at the top of every script makes stuff a lot safer. Explanation here.
It’s like calling all fuel diesel.
You tend to lose count after the first few hundred.
Or libcinder. Or even simply Arduino.
You can start here: https://hackaday.io/project/176931-hp-printer-cartridge-control-module/details
HP printers are conceptually quite simple devices, the printer just moves the cartridge and the paper. The cartridge does all the actual printing. So you reverse engineer the pinout on the cartridge and you can make your 3d printer do normal printing. That’s also how those little handheld cube printers work.
Everyone just confirming aliteral’s point.