Though, qtwebengine only takes 38 minutes on my 32-thread Threadripper. Full emerge -eva @world only takes two hours or so.
Try Xorg, Firefox, KDE, et al, on circa 2008 hardware (bearing in mind I switched to Arch not long after building a new system in 2012).
It's a labor of love.
That's Gentoo for you.
I actually have the old FreeBSD Daemon tattooed on myself.
I have a small miniature of the FreeBSD daemon (copper plated, about 2" high) made by some jeweler in Australia back in the early 2000s. Sadly the tail broke off on the way over here, but it is what it is.
Obviously not a permanent piece of body art, but we all have our own, uh, eccentricities.
(It came with both the trident and an apache.org feather.)
Indeed. Never did test it on new hardware since I'd switched by that point.
I do occasionally keep some proficiency with Gentoo via LXD though, but since the images are small the recompilation is obviously pretty fast.
That's what I love about OSS: use what works for you!
Yep, absolutely.
I'm a KDE user on NVIDIA, so I'm somewhat cautious about Wayland. I'd guess EGLStreams is the only option in that case since they apparently have their own idea of doing things. I also sometimes run graphical apps from inside containers. Xorg is probably the only option at this point.
Incidentally, Vulkan is a consequence of AMD's failed Mantle.
If you dig into some of the DirectX12 behaviors, there appear to be a number of similarities to Mantle as well that can't possibly be chance.
You can run Wayland sessions on NVIDIA hardware
Well, yes, as I mentioned I've encountered EGLStreams in the docs, but I'm not hugely inclined to switch at this point.
KDE support for Wayland should be seeing a fairly significant update in 5.20 which is out but not in the Arch repos as of this writing.
I may explore at some point, but I really don't have any reason to abandon xorg. There are also some ongoing window manager issues in KDE that haven't been fully resolved under Wayland (5.20 appears to fix a number of them). Further, 5.21 is expected to bring additional improvements as well.
Performance under Plasma appears to be a persistent issue.
I do LXD for some stuff,
I use it mostly for containerizing a number of workloads and for development purposes. Also because screw Docker which is analogous to "we don't have an easy way to install our app, so we're shipping you our entire machine."
Great. Just what I wanted. Yet another Alpine image that mysteriously balloons because Python wheels containing C sources require downloading the sdist since it has to be rebuilt for libmusl.
Don't get me started on the Sentry devs change toward using Clickhouse a number of months back, which is impossible to build from source on AMD CPUs unless you actually patch their cmake scripts. Because lolintel.
but anything that needs full-fledged graphics is done with a qemu kvm passthrough setup
To be fair, GPU acceleration is super easy LXD. Leastwise, that's one advantage with NVIDIA. Though, the only reason I've come up with using it is for browser isolation without the additional overhead of a VM (and less of the security).
Need any help with anything, give me a shout. I'll be glad to help!
I appreciate it. As a software developer, if I have a hankering for doing something I've not actually tested before, the journey is just as important to me as the destination.
At this point in time, I just don't have a reason to run Wayland and many reasons not to run Wayland.
Try Xorg, Firefox, KDE, et al, on circa 2008 hardware (bearing in mind I switched to Arch not long after building a new system in 2012).
That's Gentoo for you.
I have a small miniature of the FreeBSD daemon (copper plated, about 2" high) made by some jeweler in Australia back in the early 2000s. Sadly the tail broke off on the way over here, but it is what it is.
Obviously not a permanent piece of body art, but we all have our own, uh, eccentricities.
(It came with both the trident and an apache.org feather.)
Indeed. Never did test it on new hardware since I'd switched by that point.
I do occasionally keep some proficiency with Gentoo via LXD though, but since the images are small the recompilation is obviously pretty fast.
Yep, absolutely.
I'm a KDE user on NVIDIA, so I'm somewhat cautious about Wayland. I'd guess EGLStreams is the only option in that case since they apparently have their own idea of doing things. I also sometimes run graphical apps from inside containers. Xorg is probably the only option at this point.
Incidentally, Vulkan is a consequence of AMD's failed Mantle.
If you dig into some of the DirectX12 behaviors, there appear to be a number of similarities to Mantle as well that can't possibly be chance.
Well, yes, as I mentioned I've encountered EGLStreams in the docs, but I'm not hugely inclined to switch at this point.
KDE support for Wayland should be seeing a fairly significant update in 5.20 which is out but not in the Arch repos as of this writing.
I may explore at some point, but I really don't have any reason to abandon xorg. There are also some ongoing window manager issues in KDE that haven't been fully resolved under Wayland (5.20 appears to fix a number of them). Further, 5.21 is expected to bring additional improvements as well.
Performance under Plasma appears to be a persistent issue.
I use it mostly for containerizing a number of workloads and for development purposes. Also because screw Docker which is analogous to "we don't have an easy way to install our app, so we're shipping you our entire machine."
Great. Just what I wanted. Yet another Alpine image that mysteriously balloons because Python wheels containing C sources require downloading the sdist since it has to be rebuilt for libmusl.
Don't get me started on the Sentry devs change toward using Clickhouse a number of months back, which is impossible to build from source on AMD CPUs unless you actually patch their cmake scripts. Because lolintel.
To be fair, GPU acceleration is super easy LXD. Leastwise, that's one advantage with NVIDIA. Though, the only reason I've come up with using it is for browser isolation without the additional overhead of a VM (and less of the security).
I appreciate it. As a software developer, if I have a hankering for doing something I've not actually tested before, the journey is just as important to me as the destination.
At this point in time, I just don't have a reason to run Wayland and many reasons not to run Wayland.