I’m a monthly donor to KDE EV and to the Mozilla Foundation.
I’m a monthly donor to KDE EV and to the Mozilla Foundation.
Bash
Not because it’s the best or even my favourite. Just because I create so many ephemeral VMs and containers that code switching isn’t worth it for me.
It’s probably just a version of the “Office key” that would simulate pressing like 5 modifiers (that’s where the Ctrl+Alt+Win+…+L opening LinkedIn comes from), but includes a final key. Windows might make it a pain to do, but on other OS’s you could bind that key to whatever you want.
Probably the black sea, dad.
Yeah that’s solidly it. I use strictly confined CLI snaps all the time. (In fact, I maintain the snaps for a couple of CLI apps.) They work fine as long as the snap has the right plugs.
But I don’t want to have to run flatpak run dev.htop.htop
to get to htop.
I’ve got a desktop that got a dirty install of KDE Neon when the repositories first got put up (before there were isos). Been in-place upgrading it ever since.
Yep! Most of us are even homo sapiens!
Kubuntu works well on mine. A friend has Lubuntu on his.
Here’s a real-world use case that also won’t require insane GPU power.
Here’s a real-world use case where this difference is noticeable to the average person. We don’t need to render video games at 1000 Hz, but many things that can be rendered with comparatively low GPU power could be made a better experience with it. The real question is whether/when the technology becomes cheap enough to be practical to use in consumer goods.
Here’s a big part of why they want 1000Hz. You don’t need to fully re-render each frame for most cases where 1ms latency is desirable - make a 100 Hz (or even 50 Hz) background and then render a transparent layer over it.
I thought one of the main advantages of sodium-ion batteries was price? Great for the applications you listed
Some distro that uses the Ubuntu repos blocked users from even installing snapd manually without jumping through a bunch of manual hoops. It’s one thing to not preinstall it, but that reeked to me of exactly the “we know better than our users” attitude they were accusing Canonical of.
Some distro that uses the Ubuntu repos blocked users from even installing snapd manually without jumping through a bunch of manual hoops. It’s one thing to not preinstall it, but that reeked to me of exactly the “we know better than our users” attitude they were accusing Canonical of.
How about the maintainers blocking a package that’s included in the default repository for ideological reasons?
The problem isn’t that every gnome dev is bad - not by a long shot. The problem is that there are just enough gnome devs in just the right (wrong?) positions who have an “our way or the highway” philosophy that it causes problems not just for people trying to use GNOME, but for people (such as the Kate developers) who are trying to give their users a good experience.
And by being the default in so many distros, GNOME has enough clout that if they choose to abandon a standard, many people will change to whatever GNOME does, making their applications worse for people on other desktops.
In the end it’s not too dissimilar to the problems created by the dominance of Chromium and Windows. The biggest difference IMO is that Google are actually more conciliatory towards others than the GNOME team are in many cases. Which is kinda crazy given how much Google can throw their weight around on the web.
This raises further questions, since it seems his humanoid form is a facade provided by his magic powers. Do you get him in non-corporeal form, or do you get him like that episode where he became human?
As long as you have polkit setup to work in terminal sessions, yes. This is pretty standard these days, though not particularly widely used.
The packages in most distros will also restart the server for you. Any existing SSH sessions will technically be running in vulnerable versions, but if I’m understanding the vulnerability correctly this isn’t a problem, as they won’t be trying to authenticate a user.
If you want to be sure, you can manually restart the ssh server yourself. On most distros
sudo systemctl restart sshd
should do it.