@devfuuu @cm0002 still using grub installation and configs i generated in 2011. Questions?

@qqq @OpenStars before wow64 introduction, wine required 32 bit process and multilib to run 32 bit code, requiring 32 bit opengl/bulkan implementations
But it is possible to run 32 bit code in 64 bit process.
Wine in wow64 mode enforces 64 bit process to use only lower 32 bits address space and thunks 64 bit libraries via wine nt syscall interface to loaded 32 bit PE binaries. No multilib or even 32 bit process support required, 32 bit instructions executed as is. Also this allows using machine code translation layers (like fexemu) exposing native calls with same syscall interface.
wow64 maybe still limitted because it does not allow calling native libraries directly and increases overhead. win32 TLS code is using same fs segment register as linux 64bit TLS and workarounds may have bigger overhead, than using multilib

@Mwa @NONE_dc *uninstall

@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

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