@Zwiebel yes :(
Or use some automatic kernel update scripts.
For me, it’s better if i update kernel/grub manually, than do some automatic update and find system not booting anymore. But most users prefer automatic update, which sometimes may fail on some systems

@VinesNFluff @westyvw but win9x still using dos drivers, so it is dos application. 32 bit dos application running on untouched dos system. Yes, it implements full 32 bit OS

@Breve i prefer spending couple hours to configure (and half-a-day to rebuild packages) to update my home linux system every half-a-year than using windows. And it seems, there is no windows alternative for non-IT-professionals now because every distro is broken. I still may recommend linux mint as windows alternative, but not sure it really will be better that windows because it’s ubuntu based and will catch all ubuntu bugs.
Also, most binary distros build mesa with nouveau enabled, which breaks it. It links lingbm to glappi, which causes dependency hell. Also it adds some slow nouveau call to winsys implementation even if you do not have nvidia, shich causes big slowdown. And linked-in nouveau code in libgallium increases memory footprint This only should be used when you relly use nouveau, but most people replace it with binary blob or not using nvidia at all…

@Breve @_carmin this is because distros use autogenerated grub configs, and using rootfs for grub.
Whan maintaining grub manually on separate or EFI partition, nothing breaks. You only need edit grub config every kernel update. For x11,wayland, etc only solution is some source-based system (gentoo for example) where you decide what to build and what to update. In other cases expect unwanted breakage becauseyou cannot stop binary distro from bringing unwanted changes

@shuro I XP have better hardware support because it targets workstation and home systems, while 2000 mostly targets servera. And it was released 2-3 years later

@shuro it seems, support of this laptop was added after win2k release. Anyway, usually we not expect hardware to work out pf box on windows (at least before win10 which downloads drivers automaticly). Without downloading drivers it requires windows version released at least after hardware was made

@shuro supporting formats and hardware out of box never was good side of windows. But 12 years ago i used some PC which did not require installing any driver on windows 2000, EVEN TV TUNER worked out-of-box. None of linux live cd was capable to run it’s sound and network card and there are no drivers for tuner and 3d acceleration on this pc. Network and sound required building some kernel modules, disabled by default

@shuro i do not think browser-based statistics is good. Anyone who do not want different from elsewhere will set windows UA and breaks this statistics. just imagine, how may bots may set windows user agent not being running on windows

@Diplomjodler3 @drq win7 is shit, really shit. It renamed “My computer” to “Computer”…

@shuro @teft this was last version that not broke interface consistency.
And not’ it was not stable. It was buggy like any OS at this time. But at least they found how consistent desktop interface should look.
I like how internet explorer 5-6 seamlessly turns to explorer windows and back. How everything looks good using system theme
Or menus and system dialogs, easily extendable by custom modules, registered in registry. Or like internet explorer, using gdi is drawing very fast when launched with RDP even with slow internet connection… Imagine something like this in wayland, which only operates pre-rendered bitmaps, it’s just impossible now. And where developers cannot use one toolkit that usin system theme and extending system settings of kde/gnome for 3rdparty app is just impossible.
And all of this runs good on 32mb ram.
Even now both windows and linux modern desktops are long far way from this.

@shuro @lritter what this unknown desktop os?

@drq @linuxmemes Even nt5.0 was shit, but it’s interface was really good. Later microsoft lost interface consistency. First is enabled/disabled visual styles, and second it dotnet interfaces, looking completely different This is enshitification :)

@asudox it is missing basic OS feagures. Initially it was OS, but now it’s just firmware for google devices, not OS.

@asudox android even cannot share folder between 2 apps with different signature. It cannot be called OS.

@pewpew @asudox DOS is operating system too, But linux with android userspace is not an operating system :)

@Natanox @mtchristo
>Flatpak and Snap for distribution, GTK4 (opt. with or without libadwaita) or Qt6 for the UI, Gnome and KDE to take care for proper integration, and stuff like Wayland, Pipewire
I do not have anything of this in my system and will not install any app that requires to support all of this.
Flatpak even cannot work without namespaces (which is not enabled in kernel defconfig). If you want to make flatpak default option to distribute apps, first make sure it does not require enabling some (possibly insecure) kernel configurations and work on default kernel
Wayland (in current implementation) is error. Flatpak/snap is error.
Before all of this, all we need to make app work is some x11 libraries, so app can bundle it’s needed portable toolkit and run without any additional requirements. Now we cannot just provide wayland-client, because app cannot draw with it. It needs opengl, which needs many libraries, which… cannot be provided in compatible way, so you need container bullshit that runs other distro inside… only to run some graphical app that draws few buttons…
Really, i’ll prefer using windows, not this bullshit.
Now flatpak causes people ignoring new glibc compatibility bugs, so it soon will be impossible to build portable binary for glibc systems… Even now Portable Executable (windows exe) is most portable way to distribute software for linux, because wine gives compatibilty that glibc cannot (or jusn do not want). And sometimes wine even have less memory overhead than flatpak/snap

@pewgar_seemsimandroid systemd has a lot of really good things…
But it’s too complex for init process and even too complex for service manager. Many solib dependencies causes long start, big memory footprint and possibe security issues. Many things might be implemented in some separate services, running with restricted permissions and optionally disabled.
initng was very similar to systemd, but was very simple and very much faster

@frezik @NONE_dc with WSL2 not much interesting, it’s just a VM with some custom drivers

@NONE_dc i think, vacuum cleaner’s stock firmware usually sucks the most

@imaqtpie it’s just named after musk’s bad joke