News for hackers. Stuff that matters.
Re:To Save C, We Must Save ABI by creshal on Tuesday August 11, 2026 @07:18AM (#49256414)
Is C even worth saving at this point? Even standards committee members can't consistently write C code that doesn't overflow and segfault.
Re:To Save C, We Must Save ABI by dummydummy1234 on Tuesday August 11, 2026 @07:21AM (#49256445)
What other cross-language abi do you propose?
Re:To Save C, We Must Save ABI by pjmlp on Tuesday August 11, 2026 @08:29AM (#49257224)
What everyone else is doing, COM, XPC, Android IDL, FIDL, D-BUS, gRPC,...

Especially more relevant when going with microservices, microkernels, serverless, static linking (and still have plugins),...

Re:To Save C, We Must Save ABI by bigfishrunning on Tuesday August 11, 2026 @08:36AM (#49257317)
Those are all RPC mechanisms, not an ABI. They exist at a much higher level. You could have an RPC protocol be your only interface to the OS, and that would be a valid design, but would have a performance cost (see the classic Tanenbaum–Torvalds debate)
Re:To Save C, We Must Save ABI by wasmperson on Tuesday August 11, 2026 @10:08AM (#49258668)
> Those are all RPC mechanisms, not an ABI

I'm not sure about the others, but COM is an ABI. There's a bunch of stuff surrounding it that is RPC-like but the core specification is just binary layouts and calling conventions. It's arguably more cross-language than the C ABI since it lets you generate type-safe bindings for any language, unlike in the latter where you need to parse header files.

> You could have an RPC protocol be your only interface to the OS, and that would be a valid design, but would have a performance cost

Maybe it would, but I doubt anybody would notice. The whole "everything is a file" concept on unix is basically just this (also X11/Wayland).

Re:To Save C, We Must Save ABI by pjmlp on Tuesday August 11, 2026 @09:23AM (#49257901)
Nope, when you use in-proc calls, which some of them do support, they become an ABI as well.
Re:To Save C, We Must Save ABI by zbentley on Wednesday August 12, 2026 @05:34PM (#49278894)
The subset of the list that supports in-process calls and which allows for zero-copy (and, realistically, probably mutually mutable) data sharing of its types is shorter still. I think the useful definition of "ABI" includes more than just API discoverability (aka what D-Bus provides if you take away the RPC system).
Re:To Save C, We Must Save ABI by creshal on Wednesday August 12, 2026 @03:05AM (#49268780)
Preferably one that doesn't deliberately shoot itself in the face to spite its users just to protect some committee members' egos.
Re:To Save C, We Must Save ABI by groundzeros2015 on Tuesday August 11, 2026 @09:30AM (#49258013)
Yes, it’s the most useful programming language you can learn.
Re:To Save C, We Must Save ABI by lioeters on Tuesday August 11, 2026 @10:48AM (#49259307)
> Is C even worth saving

C doesn't need saving, it will continue to survive on its own and even flourish in niches for decades to come. So will "Java"Script. Worse is Better, respectfully, or at least Old and Simple is Tough as F, living long and prosper. See, C doesn't need you but we need C, apparently for the foreseeable future.

Re:To Save C, We Must Save ABI by hn_submit on Tuesday August 11, 2026 @03:53PM (#49263557)
C will not die but it will simply fade away.

Rust is the new black and it will supplant C/C++ and almost everything else short of virtual machine languages like Java/C#.