Pizza, followed by dessert.
These are work files and shared between teams, so I'd rather maintain 100% MSO compatibility. :) Also, most of the time these files are on Sharepoint or OneDrive, so it makes it convenient to edit with M365 - don't need to save files locally and re-upload/sync them.
It's based on Ubuntu LTS, so it's not for me. Doesn't make sense that you'd want a bleeding-edge DE on an old kernel and system stack. I mean, I can understand if you're a KDE dev and you want a stable base to dev and test on, but if you're just a power user who wants to play with the latest and greatest, then using Ububtu makes no sense at all.
And refactor the code a bit to be on the safe side - change the name of the project and remove any references to litigious companies. And use an anonymous handle + VPN/proxy chains so they can't sue you.
Honestly it boggles my mind that devs contribute to emulators like these using identifiable names and traceable IPs, when everyone knows how these greedy corporations operate. Did no one learn anything from the Sony vs Geohotz case, or all the subsequent takedown against emulators? Why do these devs keep falling into the same trap again and again?
I ain't no hardcore Excel user so can't speak for others, but I've been able to completely switch to Excel Online and use Office Scripts and Power Automate for tasks for which I used VBA previously. In fact, Power Automate has been great for doing stuff like updating workbooks through scheduled or event-driven flows, without even having to open Excel. I can see VBA going away soon with these technologies.
With the state of O365 these days, there's zero need for me to have a native MSO install, and this no need for a Windows VM either (for day-to-day/personal stuff). The only reason I still keep Windows VMs though is for occasionally testing random things for work.
I don't know about car stereos, but at least for 8bitdo controllers, you can update the firmware via fwupd. And if the firmware isn't available on LVFS, you can download the blob install it manually using fwupd: https://ladis.cloud/blog/posts/firmware-update-8bitdo.html
I did this for my 8bitdo Ultimate Bluetooth controller, and it worked great.
8MB?! That is abysmally low for KDE. Depending on the apps you're using, I'd recommend allocating at least 256MB, if you're going to use it for actual productivity tasks.
Edit: Here's a screenshot from nvtop showing my VRAM usage on KDE 5.27:
As you can see, Plasma alone is using 209MB, and Kwin 175MB, and this is with nothing but just Plasma and Konsole running on a very basic desktop (no fancy widgets, just one panel). Now this is at 2880x1800, so if your VM is running at a lower resolution you'd need lesser VRAM, but you can use that as a reference to see how much VRAM KDE really needs.
It seems there's still a bit of work to be done, but it looks promising.
We are actively working on the remaining pieces to support D3D12 emulation via VKD3D-Proton. A lot is already done or in progress but there are still a few pieces missing, so don't expect D3D12 games to work just yet.
[...]
Performance is still a work in progress and continues to improve regularly. A lot of titles are running at 60 FPS or better on recent GPUs. With others, we're seeing bottlenecks that we have yet to triage. If you want to know if your favorite game performs well, the best way is to just try.
Looking at the AUR package, it doesn't look like there's any binary dependencies: https://aur.archlinux.org/packages/vulkan-nouveau-git?all_deps=1#pkgdeps
As others have mentioned, just stick to one distro (and I recommend Arch, since you're already familiar with it - also, it's much better for gaming compared to Pop).
If you really want to have that delineation between dev stuff and gaming, you could just create a separate gaming user account, and even do cool stuff like automatically launching Steam in big picture mode, or take it a step further and jump straight into a gamescope session.
Arch Testing got it before NixOS: https://archlinux.org/packages/extra-testing/x86_64/plasma-desktop/
plasma-desktop: Last Updated: 2024-02-28 10:56 UTC
NixOS: K900 committed 2 hours ago (3f650b5)
Why not?