News for hackers. Stuff that matters.
Re:OpenBSD System-Call Pinning by Rusky on Saturday February 03, 2024 @12:39AM (#39237824)
I don't think syscall-vs-C-function is at all meaningful for someone making a completely unrelated language. The system has to pick some ABI for communicating with the kernel, and syscalls don't change that. The ISA generally doesn't define how arguments are passed, it's really just in the business of providing a fancy jump instruction.

Arguably, using the same ABI for userspace C functions and for communicating with the kernel reduces the amount of work required of completely new languages, because they are likely to need C interop support anyway.

Re:OpenBSD System-Call Pinning by touisteur on Saturday February 03, 2024 @08:28AM (#39240153)
If you're designing a whole new language today, you might want to build something to fit better with the new io_uring-like interfaces to the kernel and make 'old school' syscalls a fallback or special case. Would be interesting to have this (queueing, batching, completion) as a basic layer.