Sadly, I reckon about 2/3 of Android phones no longer have a jack, or close to 100% of flagship models.
Some editors can embed neovim, for example: vscode-neovim. Not sure how well that works though as I never tried it.
I think they meant you don't know what the binary is called because it doesn't match the package name. I usually list the package files to see what it put in /use/bin
in such cases.
Podman quadlets have been a blessing. They basically let you manage containers as if they were simple services. You just plop a container unit file in /etc/containers/systemd/
, daemon-reload and presto, you've got a service that other containers or services can depend on.
Not sure what you're on about, most package managers have a literal database of most package manager installed files. Debian and derivatives have dpkg --verify
or debsums
to verify the files, arch has paccheck
, I'm sure other distros have something similar. And fixing them is just a matter of reinstalling the package, which you can do from a chroot if the system won't boot.
Or you can just run your system on a checksumming FS like btrfs which will instantly tell you when a file goes bad.
"It's longer than you think!"
The message that we approve of the removal of the headphone jack done in order to peddle wireless headphones...
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.
It's a size of paper with an aspect ratio of 1:√2, and the short edge that is 21cm long. The long edge will then be 21√2 = 29.7cm. The aspect ratio has the interesting property that it can be halved and doubled while remaining constant.
This has been your ISO fact of the day.
Not sure what you mean, they've always used Snapdragons? The S23 from 2023 uses one, and the S3 from 2012 uses them in some models, and most galaxies between those do as well.
I remember having this realisation about Mir, but only after we collectively ran it off the cliff wall. The main reason everyone piled on Mir was that it was thought that Canonical would be priming Linux desktop for fragmentation with two competing standards.
But in fact, Mir was providing a solution to the fragmentation Wayland was bringing. Now we have 3, 4, 5 Mir-s, all with slight incompatibilities. Want a feature? Better hope all of them decide to implement the extension after someone proposes it. We know how well that worked in the past.
This is also ironic because the detractors of Xorg constantly talked about the issues with Xorg extensions and how many of them there were. But I never really had to look up which extensions Xorg supported, while I have had to do that with Wayland compositors.
The mic being active or not doesn't affect her hearing. If he interrupts her she'd still hear it, only the TV audience wouldn't, so she'd seem flustered.