|
|
|
|
|
|
by udev4096
361 days ago
|
|
|
More power usage, need at least 64G of ram to even remotely use it as it's intended, no hardware acc by default, buggy templates, sleep is broken, uses X11 for display, dom0 is not updated as frequently as it should be and I hardly see any effort in documenting the fact that individual VMs's security matter too. That is not to say I hate Qubes. I think everyone, especially people dealing with sensitive data, should use it |
|
|
True, it's the price for security.
> need at least 64G of ram to even remotely use it as it's intended
This is false. I'm using it on a 32G machine never meeting the limit. If you use minimal templates, you can easily work on a 8G machine.
> no hardware acc by default
They're working on on it: https://github.com/QubesOS/qubes-issues/issues/8552
> buggy templates
What are you even talking about? I'm using Qubes as my daily driver and don't have any problems with the templates.
> sleep is broken
It works flawlessly on my Librem 14.
> uses X11 for display
Why is this a problem? See also: https://github.com/QubesOS/qubes-issues/issues/3366
> dom0 is not updated as frequently as it should be
Should be for what? No software should be run in dom0, so its updates are not relevant: https://www.qubes-os.org/doc/dom0-secure-updates/#reasons-fo... and https://www.qubes-os.org/doc/how-to-install-software-in-dom0...
> I hardly see any effort in documenting the fact that individual VMs's security matter too
https://github.com/QubesOS/qubes-issues/issues/4233
Also, Kicksecure template is already available: https://forum.qubes-os.org/t/kicksecure-template-for-qubes-t...