What I mean is that I should be able to use TensorFlow, or a Ruby library or Qt6 from any other platform and language, without someone having to write bindings to it or porting it wholesale. We've been wasting thousands of man years just rewriting the same code everywhere, with the quality of implementation being dependent on how popular the language is. So you get the best libraries on Java, and smaller ecosystems never reach critical mass because there's no good libraries. This is unsustainable.
I really am hyped for WASM components.
Wasm is just java for people who weren't around for Java.
Unfortunately, making a new isa is the easy part. The hard part is defining the abi.
.net came closest. Wasm is focusing on the wrong problem.
The standard operating system API should provide abstractions for all general real-world objects the machine is expected to represent or interact with: dates, times, durations, recurrences, abstract time concepts like "the second Monday of every month except when it falls on a holiday", people, places, events, to-do lists...
These are things that businesses have to deal with every day. The fact that we don't have those things, standard, as a part of a programmer's toolkit is a great failure of language and OS designers.
https://web.archive.org/web/20180223094826/http://www.xent.c...
Re:Lisping at JPL Revisited
by WalterBright on Saturday January 28, 2023 @06:39PM
(#34563180)
As a language designer and implementer, I have spent a lot of hours writing time&date code, and disagree that I'm to blame for them not being standard.
I've also released them with a Boost license, so anyone can use them for any purpose.
Indeed. This service (especially the time zones) should be part of the standard operating system API.