New Windows driver blocks software from changing default web browser
New Windows driver blocks software from changing default web browser
I mean, Windows is just such a weird proprietary distro.
It doesn't use the latest Linux kernel, or even a mainstream POSIX-compliant alternative like BSD. Instead, you have a strange CP/M-like monolithic kernel — I think they used to call it DOS — that's been extended to behave more like VAX and MP/M.
It also doesn't use either X11 or Wayland as a display manager. Instead, you have an incredibly unintuitive overblown WINE-like subsystem handling the display.
Because it doesn't natively use Wayland or X11, you are limited in the desktop environments that you can use. There's really limited support for KDE, despite the best efforts of volunteers.
Instead, there's a buggy and error-prone proprietary window manager that ships with it by default. A bit like how Canonical tried to make Unity the default desktop for Ubuntu.
And confusingly, they've named that window manager Windows as well!
That window manager lacks many of the features an everyday Gnome or KDE user would expect out of the box.
It also doesn't ship with a standard package manager, and most of the packages ship as x86 binaries, so installing software works differently to how an everyday Linux user would expect.
There's also only one company maintaining all of these projects. It insists on closed source, and it has a long history of abandoning its projects.
And sure, if you're a nerd who's into alternative operating systems, toying with Windows can be fun.
But if your grandpa is used to Linux, frankly he'll be utterly bamboozled by the Windows experience.
I'm sorry to be glib, because Windows does have some nice ideas.
But.
Windows on the desktop just isn't ready for your average, everyday Linux user.
#Linux #Windows #PC #OpenSource #GNU #GNULinux #BSD #FreeBSD #Microsoft #KDE #Gnome #Ubuntu #GPL #LinusTrovalds #Linus #BillGates #OperatingSystem #DesktopLinux #POSIX #UNIX #Distro
@whophd @ajsadauskas @Naich @ardi60
I've wondered about the history of the naming before [1], anyone knows why they shortened the subsystem name when they moved from UNIX to Linux?
@[email protected] @[email protected] I was wondering if they had gotten too lazy when they "updated" the previous name or something, but it seems "Windows Subsystem for UNIX-based Applications" was officially part of "Windows Services for UNIX", so that kind of name already existed, even if the subsystem itself had a better name? (Now another question I'm curious about is: were these names already defined at the time of the Microsoft Korn Shell fiasco, or did these come later?)
@[email protected] @[email protected] @[email protected] My spidey-sense tells me that "WSL" sounded cool and ticked the boxes — it perked up ears by saying "Linux"