cosmopolitan VS src

> Using a binary for each platform and chip is the past.

Cosmopolitan sends its regards: https://github.com/jart/cosmopolitan

> Rise above with lightweight container[...]

Ah yes, that famously lightweight way of distributing software, full on virtualised containers, each running an OS.

Case in point:

https://github.com/jart/cosmopolitan/blob/master/libc/sysv/s...

The system call numbers of all the unixlikes are bitwise packed into a single number. There is exactly one of those columns which is stable: the Linux one. Everything else is not part of the binary interface of their respective operating systems.

I've written about how Linux is special in this regard:

https://www.matheusmoreira.com/articles/linux-system-calls

It's a neat hack but I'm afraid it's in grave danger of falling victim to the Darth Vader of OS ABI stability.

https://lwn.net/Articles/806870/

> Program to the API rather than the ABI.

> When we see benefits, we change the ABI more often than the API.

> I have altered the ABI.

> Pray I do not alter it further.

Maybe portable CL binaries soon-ish (in CL units of time, mind you)!

Conditional on https://github.com/jart/cosmopolitan/issues/939 as mentioned in INSTALL

Cosmo gives you what you described above and it’s <10kb

https://github.com/jart/cosmopolitan

llamafiles will run on all architectures because they are compiled by cosmopolitan.

https://github.com/jart/cosmopolitan

  Cosmopolitan Libc makes C a build-once run-anywhere language, like Java, except it doesn't need an interpreter or virtual machine. Instead, it reconfigures stock GCC and Clang to output a POSIX-approved polyglot format that runs natively on Linux + Mac + Windows + FreeBSD + OpenBSD + NetBSD + BIOS with the best possible performance and the tiniest footprint imaginable.

My comment was based on cloning master yesterday and trying to build redbean but hitting what looks like https://github.com/jart/cosmopolitan/issues/940

Indeed it lioks like the commit you mentioned should have fixed the issue with the pointer having too many bits for the weird kernel used on android and some raspis. Fingers crossed that release works.

Interesting! Let's check the OpenBSD implementation of this algorithm, and here is the link to it. The first point of interest lies here:

The OpenBSD project released 7.6 of their OS on 8 Oct 2024 as their 57th release 💫

Funny enough filenames are just byte sequences. So almost anything goes.

There was just some patch that added '/' protection, because that's the only character that's not allowed in filenames.

https://github.com/openbsd/src/commit/46f7109a9e03df89b66ada...

OpenBSD gives us good documentation as a series of the project. (For example, the man pages are cared and kept maintained.) It's applied to principal service packages as well as the OS. So is as to PostgreSQL.

The OpenBSD project released 7.5 of their OS on 5 Apr 2024 as their 56th release 💫

> Only two remote holes in the default install, in a heck of a long time!

As someone who doesn't know this kind of stuff well, will this cause OpenBSD to have to update the statement above?

https://www.openbsd.org