News for hackers. Stuff that matters.
Re:liblinux: Architecture-independent access to Linux system... by matheusmoreira on Wednesday November 10, 2021 @09:51AM (#29175187)
A willingness to discard everything doesn't mean you can actually do that though. Windows, for example, simply doesn't let you get rid of the Microsoft DLLs. You can't talk to the kernel directly, the interface will change and break your program. The BSDs and macOS all do the same thing.

Linux lets you do this. The interface is stable. People can build their custom user space on top of it and enjoy a great kernel full of drivers. Wouldn't it be amazing if someone came up with a 100% Lisp user space? A 100% Rust user space?

Re:liblinux: Architecture-independent access to Linux system... by lelanthran on Thursday November 11, 2021 @05:37AM (#29186529)
> Linux lets you do this. The interface is stable. People can build their custom user space on top of it and enjoy a great kernel full of drivers. Wouldn't it be amazing if someone came up with a 100% Lisp user space? A 100% Rust user space?

Great indeed (I like Lisp!), but I have to question how useful that would be in practice.

Let's take Lisp as an example: I can now program only in Lisp and talk to the OS in native Lisp only (including POSIX calls). The downsides are that I cannot call any existing library; my 100% Lisp environment cannot use libzip, or libffmpeg/libavutil, or libSDL, etc.

In order to make that 100% Lisp environment actually useful it's going to be doing FFI calls anyway into a C ABI. That makes the OS-interface redundant.

Python is as popular as it is purely because it made calling into the C ABI easy: existing libraries were made instantly useful in Python, not unnecessarily hard.