pointless
It might be due to display drivers not playing nice on wayland; I’ve had this problem a couple months ago on arch with the amdgpu drivers, using either one of sway, labwc, or KDE. It did not happen on Xfce, though; and after a kernel update the problem subsided.
I was about to say the same – and also: nftables syntax is a lot cleaner compared to iptables, and the whole configuration can be loaded from a single file just like pf, without doing the dump/reload cycle that iptables required. Unless UFW does features like defining zones which a user might need (like firewalld), then it’s not a huge improvement on bare nftables usability-wise.
It could be worse; it could be weasels ripping your flesh.
This is the right response to the OP’s bizarre “question”, of course, but … yeah … the ‘for the most part’ qualifier is key here.
Some caveats, though: To share the same home folder safely, it’s best to use the same desktop environment on both distros. Debian paired with Fedora makes it difficult to match the release numbers of the desktops, though, and there might be discrepancies with respect to user config files in the home folder, when you’re trying to configure features in Fedora that aren’t yet available in Debian.
Also the system folder setup (locations of libraries and include files) is different between the two, so if there’s anything in the home folder that’s linked against libraries in one distro, it won’t work in the other. Especially if you’re going to compile anything in the home folder – including stuff that package managers of scripting languages like lua and python themselves compile – that could lead to major heaadaches.
I don’t think it does virtual desktops with labwc still; but when it does, labwc is as good a replacement for xfwm as any, IMHO.
labwc can do virtual desktops; there’s a desktop switcher, and the window switcher is aware of windows only in the current desktop – but I can’t figure out how to query window-per-desktop information programmatically otherwise. waybar, wlrctl, as well as xfce-panel don’t seem to have access to that info either. Still waiting for accomodations with respect to some wayland extension, I suppose.
Ubuntu’s font rendering used to be better than every other distro, because they incorporated patches on freetype that were legally ‘iffy’ as to whether they infringed on microsoft’s patents; later whatever exclusivity requirement that there was with those patents expired, and the patches got upstreamed in freetype itself.
So now all Linux desktops are capable of subpixel font rendering, hinting, whatever. But before that, font rendering really was hideous on other distros.
Smaller browsers built on webkit do exist; see ‘Epiphany’, ‘surf’, ‘luakit’, and ‘Nyxt’. Qt’s web component used to be based on webkit as well, though they’ve switched to Blink (Chromium).
Unfortunately, none of the browsers listed above are 100% sufficient to replace Firefox. They all rely on GTK bindings on webkit, which has its own quirks; and none have support for webextensions.
Who’s “we”, though? Here’s the list of Linux Foundation members: https://www.linuxfoundation.org/about/members It’s a foundation by, and for, commercial interests; not the users. If the same interests made up a foundation to develop a browser, it wouldn’t be different from Chrome; because in the realm where browsers are supposed to work, those ‘commercial interests’ would demand doing what Chrome does.
It’s a ‘happy accident’ that with respect to a unix-like OS kernel, the interests of the industry ended up being compatible with the interests of the user.
Python programmers appear to actively promote the ‘easier to ask forgiveness, than permission’ style nowadays. This article has a measured take: https://realpython.com/python-lbyl-vs-eafp/
I’ve got these articles saved, about the history of brushed metal on Apple software: https://512pixels.net/2013/03/brushed-metal-intro/ https://512pixels.net/2016/11/the-brushed-metal-diaries-beyond-software/
To be honest I loved it … though maybe it has to do with the fact that I have a soft spot for 10.4 Tiger, due to personal (?!) reasons. After Tiger they started progressively tearing down the brushed metal components.
You wanna get tivoized? Ha? Because that’s how you get tivoized.
and like a goddamn fiddle!
With Proxmox on AMD gpus, it can be as simple as picking a pci device from a dropdown.
– but then again, you’ll need to learn how to properly use proxmox, esp. with respect to storage configuration. Also, the performance can still suffer, depending on various factors.
If it’s not too big of an inconvenience, dual boot is the way to go, IMHO.
It’s either this fairy tale, or its flip side, the myth that ‘private vices’ somehow add up to ‘public virtues’.
A pedantic thing to say, surely, but the title really should’ve been: “Linux Directory Structure” – ‘Linux filesystems’ (the title in the graphic) refers to a different topic entirely; the title of this post mitigates the confusion a bit, though still, ‘directory structure’ is the better term.
There’s a less capable Mv3 port of uBlock Origin by the original developer, called ‘uBlock Origin Lite’: https://chromewebstore.google.com/detail/ddkjiahejlhfcafbddmgiahcphecmpfh
I use Chromium only very rarely, so I don’t know how effective it is, though.
If you’re using the ‘Pro’ or ‘Education’ license for Windows 10, you can look into Hyper-V, which should allow you to boot a VM from a physical disk.
Hyper-V is built-in to Windows; & you just need to enable it in system settings.
Not sure if it works with partitions, if you’re dual booting the OSs from separate partitions on the same disk – it probably doesn’t; in which case you might need to migrate Mint to its dedicated disk first.
Wouldn’t enabling the --system-site-packages flag during venv creation do exactly what the OP wants, provided that gunicorn is installed as a system package (e.g. with the distro’s package manager)? https://docs.python.org/3/library/venv.html
Sharing packages between venvs would be a dirty trick indeed; though sharing with system-site-packages should be fine, AFAIK.
All stdout gets piped through lolcat now.