News for hackers. Stuff that matters.
Re:Pi 1.0 by Zambyte on Thursday October 01, 2026 @09:10PM (#49928858)
Those three languages would be very difficult for creating a system with the level of extensibility that Pi has.
Re:Pi 1.0 by semiquaver on Thursday October 01, 2026 @09:24PM (#49928936)
Why? Lots of systems written in those languages are extremely extensible.
Re:Pi 1.0 by Zambyte on Thursday October 01, 2026 @09:33PM (#49928989)
You either need to rebuild the harness every time you want to make a change, or a lot of deliberate effort is required to maintain an API surface for extensions, distinct from internal implementations, or you can embed an interpreter like Lua, Python, or... JavaScript. Or you could instead go the Pi route and use an interpreted language, and just load extensions into the interpreter, alongside the program itself. When one of the main goals is extensibility, the latter seems like the obvious choice.
Re:Pi 1.0 by nicce on Friday October 02, 2026 @06:29AM (#49931923)
I feel like people have forgot how extensions used to work long time ago with compiled languages. Extensions can be just dynamically loaded, (e.g. DLL from Windows world, .so from Linux). There is no need to compile the whole harness. This is also possible when using Rust, but people are just lazy.

And yes, API must be maintained for compatibility, but that is needed anyway.