@Kolanaki @The_Picard_Maneuver i’m not sure if any existing hardware can handle vrchat smoothly. This piece of udon and photon cannot work smoothly with more than dozen players

@NullPointerException @yesman debian never updates it

@hdsrob
>That’s basically Avalonia UI.
no, avalonia cannot help you run existing applications. Also. Avalonia is a crap, taking minutes to parse xml crap on poor hardware
Yes, there are many implementaion of WPF-like UI, but no implementation of existing Windows UI.
mono’s winforms allows you run existing winforms apps without single line change or even without recompiling (just replace related System.Windows.* assembies)

@DacoTaco Yes, it’s Microsoft decided to kill classic win32 widgets and any XAML support in Mono, forcing new WinRT platform and not providing any GUI support in netcore. It’s sad that nobody made some crossplatform WPF implementation for modern dotnet, Maui is not incompatible with existing source code, IIRC

@kirk781 no, it is not because of linux support. It’s only because managers hiring web developers instead of desktop apps developers. Because… managers do not see real difference, but see some stylish web design.
Microsoft ruined cross-platform desktop apps many years ago in early WPF/Sliverlight/XAML era by ceasing Moonlight project:
https://en.wikipedia.org/wiki/Moonlight_(runtime)
https://web.archive.org/web/20120716033915/http://lists.ximian.com/pipermail/moonlight-list/2011-December/001392.html
So there is no reason to blame Linux that we do not have modern cross-platfrom toolkit for GUI apps.
Microsoft decided to make new XAMP/UWP incompatible with classic widgets GUI and kill classic GUI in WinRT/Win8 era, Microsoft decided to make XAML GUI Windows-only and cease mono developement entirely, not providing any GUI supportt

@DacoTaco @MoogleMaestro there is a port of mono winforms implementation to modern dotnet and it’s really works:
https://github.com/DanielVanNoord/System.Windows.Forms

@jollyrogue @XenGi it is not particularly good outside of Gnome environment

@UnfortunateShort @kirk781 there is PWA for such apps

@Jankatarch @mod_pp but msys2 is not windows…

@squaresinger but it stable trying remove unrelated software when installing steam or 32-bit software. Installing steam caused DE removal even more then ten years ago

@squaresinger @boonhet typical apt…

@The_Picard_Maneuver https://combineoverwiki.net/wiki/Gonome

@Sustolic @VitoRobles 15 years ago initng in linuxmint was doing magic; booting system to gnome2 desktop in 3 seconds from grub. On PCs with intel motherboard this was about 4 seconds from poweron. And moreover, this was on HDD.
Now all systems are bloated and cannot boot in 3 seconds even on SSD

@Magnum @Lukemaster69 proton usually runs in container

@JackbyDev @nutbutter
People dislike unwanted change. Imagine, you are using some distro for years, and after some update everything changes and you cannot configure system usual way. Many software is changing behaviour You need read tons of docs to change something or worse, while your system hang at boot.
My first try using systemd ended in kernel hang after too much systemd’s dmesg flooding (that was slow arm board, so it’s unlikely someone might help me with debugging it)
But yes, many people just hate systemd because it was forced change, not even because it’s too complex

@SkaveRat @possiblylinux127 systemd should be in CW (but do not know if lemmy supports CW)

@Ging this was reference to one funny musks post about mastodon few years ago (post was deleted later)
Also, mascot is green elephant reference:
https://en.wikipedia.org/wiki/The_Green_Elephant

@Ging @nutbutter it’s freedom of init system choice!

@woelkchen @kurcatovium
Implementing preserved-libs was sugested even in 2011, but arch/pacman devs do not want preventing package breaks
https://bbs.archlinux.org/viewtopic.php?id=118995
Ths would solve all dependency problems with inconsistent versions, partial updates. It will keep library until all depended software removed, preventing breakage

@Axolotl_cpp in most binary distros you cannot disable most of mesa drivers, you do not need.
you can try something like

cat /proc/$(pgrep <process>)/maps|grep libdrm

for any gui process to ensure that all existing drivers are loaded. You will keep LLVM in any gui process even if your drivers does not need it (because others, that need it is linked to llvm)
Only source-based distros allows really disable it