The fad has been going for 25 years.
You can have any Python version and package you want.
It's probably too simple to be an all-purpose init/supervisor. It doesn't have dependency management and the default way of setting up per-user services is kind of limited. That said, I've never missed the former and the latter can easily be fixed with turnstile.
You can do virtual environments with literally any Linux distribution. You cannot use virtual environments for Python packages that depend on other Python packages (I mean, I guess you could. But that defeats the point of packages). That pages doesn't tell you how to run multiple SYSTEM Python versions, because you can't in Void. Gentoo lets you run multiple Python version via the eselect tool. You can use individual Python use flags or the global PYTHON_TARGETS and PYTHON_SINGLE_TARGET settings in the make.conf.
Pretty sure it's an inherent Python feature since venv's also exist under Windows. It's basically self-contained/portable Python.
I'd say fuck around with Libre Office and GIMP, see if you can scan and print shit. Install Handbrake/vlc/libdvdcss+libbluray and rip some movies, install a virtual machine, some emulators and Super Tux. Play around, have fun, see if you can be productive too. There really is a lot of good software for Linux these days if you put in the effort to seek it out.
This is an environment variable. You had to use it for any form of wlroot based wm (Hyprland included since aquamarine is just wlroot but rewritten in C++.
Wayland by default will never tear since it always uses vsync. Experimental support for tearing was finally merged a year ago and it only got to the point of usability 6-7 months ago.
If you want to deal with a little less partitioning hassle, you can keep two drives with two operating systems. I'm pretty sure you can configure GRUB to add an option to boot from the other drive, but if anything you can always use the UEFI boot menu to switch between them when needed. Set the boot order in UEFI to prioritize the Linux partition, set up GRUB, or not, done. Just about all the hassle of dual booting Windows and Linux happens when you're trying to put both on the same drive, since Windows really doesn't like it when it's not in charge of the EFI partition.
depends how you set it up, if you keep it separate windows is less likely to fuck with it.
Depending on distro it may do it all for you. I use Mint (not the most adventurous I know but it just works) installed on an NVME and just left the previous Windows 10 install untouched on the other NVME. As long as the UEFI is set to look at the Linux drive first, on power up it presents an option screen to boot into either (and some safe boot options as well) with it continuing to boot into Linux if nothing else is done in ten seconds. I did nothing to set that up. Seems to be just part of the default install.
I know it's an environment variable. I'm saying hyprland has had a config option to enable screen tearing without needing to add that environment variable for at least a year.
Yeah you just install os-prober along with grub. Then you uncomment or add the line if it isn't there to enable os-prober for finding other bootable drives. And it should just work after regenerating your config.
So I found much of the daily huge writes are from this auto update thing, maybe "gnome-software". Any way to set that to manual so updates when I want, not every single day?
And so we return to where we started?
It's either some updating thing, fstrim, or both. If it is fstrim and it's not broken, I should leave that as is even though it does it daily despite weekly schedule. But if it's the former, I want to find a way to make updates manual rather than automatic. For some reason auto-updates have always annoyed me. Even on a HDD with unlimited writes.
XDG Shell is supported by every compositor: https://wayland.app/protocols/xdg-shell#xdg_toplevel:request:set_parent.
Luckily this retard has no voting power. He's known for shitting up protocol discussions though.
It isn't the same thing. An X11 window manager just manages windows, as in placement and size. A wayland compositor is responsible for compositing and displaying them as well, whereas under X you'd have a compositor like picom or the X server itself to do that.
At this point there are a bunch of bases:
if only there was like one compositor that everyone used and contributed to.
Since you mentioned it, what is the best compositor for X? It seems like all the standalone ones (picom, compton, compiz, compipicom picompi pipipicomcomcom) are abandoned or deprecated or who-knows-what.
I know what you're saying, but if that happened under wayland then gnome would end up controlling it and blocking anything that didn't fit the redhat vision from ever getting in.
As far as I am aware, picom or one of its variants is the most widely used, but I don't use X and can't give you any opinions on that. The default is no compositor.
For your own mental health stop autisticly watching your I/O. It doesn't even seem to actually be effecting anything. Other than you seeing that it happened.
Yeah. Picom is. I forget the name of the fork but their is one people particularly like.
nah
