For those who want to keep macOS due to some reason: https://github.com/blueboxd/chromium-legacy
For those who want to keep macOS due to some reason: https://github.com/blueboxd/chromium-legacy
It could be an amazing change that results in much more progress for hardware acceleration on guests of various types (since that is what vmware is good at) in kvm…
Yeah but VMware was good. And I’m not seeing Broadcom investing into porting the “proprietary goodness” of VMware into KVM. I just see then looking at KVM and saying “that’s good enough” and seeing it a cost reduction measure.
I’ve questions about this.
People are talking about it like it is the greatest thing ever, however, isn’t this yet another result of the Broadcom acquisition? After firing a bunch of people , now this. Maybe they just don’t want to maintain the “existing proprietary virtualization code” so they’re moving to KVM. Less costs, less people.
Like what?
Windows 10 Enterprise with a ton of group polices applied, no issues ever. The Windows Terminal app is really good.
Love it 😂
It’s not “my hardware” it is that everyone talks about Linux desktop yet nobody puts any effort into going into the tablet market that is where Linux can have a real advantage (because ARM + full desktop OS experience) and get a large user base.
Instead of wasting time on supporting bullshit hardware that almost nobody owns and will be forgotten in about 6 months, what about placing some effort into real hardware that real people want to use like tablets? Fucks sake.
Update: just to make it clear, I own no hardware of that type, it’s not “doesn’t work on my hardware” type of situation. It is that everyone likes to talks about Linux desktop (including Canonical) yet nobody puts any effort into going into the tablet market that is where Linux can have a real advantage (because ARM + full desktop OS experience) and get a real user base.
You should not trust those builds. Everything you need to know is documented here: https://learn.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services
Windows 10/11 Enterprise is recommended as that’s the version where Microsoft can’t fuck up.
No, that’s a myth. Registry edits may revert in some cases yes, but group policy is different as it designed exactly to configure machines in a stable way.
Group policy may be beyond the general skill level, which makes the constant Linux suggestions even more laughable.
Ahaha yeah, I’ve said that SO MANY times. People have issues setting a few toggles on a point-and-click UI but then it is okay to suddenly move to a entirely different OS that most likely won’t have the software they’re used to and requires terminal skills to deal with most things. Laughable indeed.
Completely bullshit, garbage clickbait title.
Windows 10 is near EoL, however that’s for Home/Pro/Enterprise versions, you can move to one of those for more time:
To be fair I don’t really believe that Microsoft will kill it when they say they will. And even if they do it, porting security updates from those LTSC versions into the regular ones might be doable.
Now on Windows 11:
You can just disable copilot and all the other garbage using group policy, now that hard and you’ll end up with essentially Windows 10. https://www.xda-developers.com/how-disable-microsoft-copilot/
AirPods work so… how much more proprietary can you get? :P
Yeah, it may be less customizable but at least is fast and error free (unlike NextCloud)
The thing with Ubuntu / Canonical isn’t that it doesn’t work, it is that they’ve bad policies and by using their stuff you’re making yourself vulnerable to something akin to what happened with VMWare ESXi or with CentOS licensing - they may change their mind at some point and you’ll be left with a pile of machines and little to no time to move to other solution.
For starters Ubuntu is the only serious and corporate-backed distribution to ever release a major version on the website and have the ISO installer broken for a few days.
Ubuntu’s kernel is also a dumpster fire of hacks waiting for someone upstream to implement things properly so they can backport them and ditch their own implementations. We’ve seen this multiple times, shiftfs vs VFS idmap shifting is a great example of the issue.
Canonical has contributing to open-source for a long time, but have you heard about what happened with LXD/LXC? LXC was made with significant investments, primarily from IBM and Canonical. LXD was later developed as an independent project under the Linux Containers umbrella, also funded by Canonical. Everything seemed to be progressing well until last year when Canonical announced that LXD would no longer remain an independent project. They removed it from the Linux Containers project and brought it under in-house development.
They effectively took control of the codebase, changed repositories, relicensed previous contributions under a more restrictive license. To complicate matters, they required all contributors to sign a contract with new limitations and impositions. This shift has caused concerns, but most importantly LXD became essentially a closed-off in-house project of Canonical.
Some people may be annoyed at Snaps as well but I won’t get into that.
Will they learn how to apply padding to stuff this time?
vbox is easy until it starts saying vt-d isn’t enabled and refuses to start when it fact it is.
Maybe it can be installed in Debian 12 now without much trouble…
Systemd does a lot of stuff I guess it is easier to just lean based on what comes up / you need. There isn’t a single path.