3 ms·
The thing is there's nothing preventing making a portable API providing the most important capabilities datatypes did. It's one tiny little library. The challen
by vidarh 5y ago
The thing is there's nothing preventing making a portable API providing the most important capabilities datatypes did. It's one tiny little library. The challenge is cultural, not technical. Without a reasonable hope of adoption, there's little value.
It's also not as simple as it being part of the OS, though space constraints certainly would favour OS libraries - the Amiga world is full of APIs that were adopted across the board despite not being part of the OS.
E.g. XPK is a good example: If you want to support compression in an Amiga app, you'll most likely use XPK, which gives you instant support for every compression algorithm someone wrote an XPK library for.
What is more likely to have mattered was in general whether or not a potential user would be likely to already have a library installed. My first hard drive was 20MB. What an application chose to install was a big deal, and that certainly encouraged people think about sticking to options that were popular and that likely to would save space.
Regarding the "hard border", it's worth keeping in mind that while datatypes could be used for visual elements, it could also be used for "headless" load/save/conversion. Putting something like it in e.g. Gnome would be less valuable than providing the "headless" part, because the format conversion is the most valuable aspect. And that part is incidentally also the easiest part to make portable.
- rbanffy 5y agoI mentioned Gnome because it’s an application platform as much as it’s a graphical environment. You write apps for it using its services to integrate with the desktop. Datatypes don’t make as much sense at the lower OS level because the OS is not supposed to be aware of the data types applications work with.
- vidarh 5y agoIt makes little sense to talk about "lower OS level here". It's a library and a spec that can provide most of its functionality in an entirely portable manner. Datatypes basically consists of two separate parts: The class structure that provides the loading and saving and format conversion, and a widget ("gadget" in the Amiga world) that displays the loaded data. The latter would be hard to do on Linux without tying it to a desktop environment, but the former just needs a way to load data, save data and load and execute plugins.