![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
I guess that depends on what we are using it for. I use it for CAD / CAM software that only works in Windows (Vectric Aspire). Nothing else has been able to give me 3d previews with any kind of usable performance.
I guess that depends on what we are using it for. I use it for CAD / CAM software that only works in Windows (Vectric Aspire). Nothing else has been able to give me 3d previews with any kind of usable performance.
Odd, since in my experience, it’s the most consistently reliable, performant, and easy to setup / use desktop vm package I’ve used. It always seems to “just work” when others don’t
… And your reply shows exactly why no one should take anything you say seriously. You’re just trolling.
As long as you keep relying on this cliche excuse, Linux is never going to be treated as a serious desktop operating system.
Distros are trying to create usable, friendly systems. They failed at that if their distros are this fragile. That’s what “unacceptable” means in this context. You can’t just throw your middle finger up in the air at the user when their system fails by saying “you didn’t pay for it” and scurry off giggling. Yet Linux advocates keep pushing Linux on inexperienced users, saying that it’s the solution to everything; that it’s so easy their grandma uses it.
I don’t use Linux as anything more than a toy for this very reason. I’ll start taking it seriously when its advocates do.
Don’t forget about the turbo encabulator!
The distro should be testing the driver within their update system before including it in their repo. The package should include metadata about system settings that could potentially break the system.
Yeah. Why would anyone expect one of the most popular video cards in the world to work in Linux. Those idiots.
Just to be clear. I understand why a proprietary card may not work. It isn’t Linux’s responsibility to make it work. However, what isn’t acceptable is for the automated update system of an OS to break a working system. Proprietary driver or not. The update system should have thrown up some very strong warnings that proceeding would break the system.
Ohh no apology needed. I think doing it as a flow chart is a good idea. I just included the screenshot to make sure there wasn’t something going on where the colors were different for you vs everyone else.
I’ll let you know if it makes sense when I can read it 😁
Right now this is literally what I see:
You need to seriously up the contrast on those colors. Pink text on a slightly lighter pink text block is virtually unreadable.
Color changes are VERY slow.
So it’s the equivalent of KDE or Gnome?
And this is why I’m confused.
That is correct, but it doesn’t explain what Budgie is.
I don’t know what it is, and neither the article nor the Budgie website seem keen on explaining it.
One time I rebooted. The system never recovered.
Too many duplicate posts because of people cross posting the same content to all the duplicate channels across all the federated servers. I regularly see 5 duplicates in a row while browsing. It’s very annoying.
Your post is incredibly informative and helpful, so this isn’t aimed at you at all, but this kind of fix is why Linux is not ready for the everyday average user.
I’ve never been able to get GPU acceleration working in qemu/kvm. That’s also why the “just works” aspect of virtual box is important.