Conversation
Notices
-
Embed this notice
Why has no one built good linux binary compatibility?
-
Embed this notice
@lunarised The kernel, Linux's SYSCALL ABI hasn't changed much for decades, thus 20 year old binaries that only use Linux SYSCALLs work fine - for example the then largest prime number found that also implements DeCSS in i386 instructions still runs fine today if you have Linux compiled to support 32 bit SYSCALLs.
Linux's limited SYSCALLs don't offer a lot of needed functionality and are not portable, thus most binaries for GNU/Linux are compiled against GNU libc.
glbic's binary compatibility is good, as it has forward ABI compatibility and the API is forwards and backwards compatible.
Of course, such forward compatibility doesn't help if you write the software wrong - for example proprietary malware that implements digital handcuffs that checks for elf sections and refuses to run if an elf section change (that was announced 5 years ago) is made is software programmed wrong.
-
Embed this notice
@Suiseiseki for extensibility, it falls so much shorter than COM for windows
-
Embed this notice
@sysrq @Suiseiseki I never know if this guy is a bait account or just a zealot tbh
-
Embed this notice
@Suiseiseki @lunarised
>glbic's binary compatibility is good, as it has forward ABI compatibility and the API is forwards and backwards compatible.
I know this is bait but I nearly burst a blood vessel.
-
Embed this notice
@lunarised >He cannot comprehend that the GNU/Extremist instance would have GNU/Zealot's on it.
@sysrq I've never had any problems running or compiling free software binaries due to glibc.
Have you tried not running proprietary malware?
-
Embed this notice
@lunarised COM is an OS thing that a kernel cannot implement.
COM is depreciated now anyway.
Just use dbus if you want cursed IPC.
-
Embed this notice
@Suiseiseki I can assure you, deprecated or not, it is still used extensively with windows applications