3 ms·
It's tricky, because it's difficult to separate the things we remember with a feeling of nostalgia but that do not really matter from the things that were genui
by vidarh 6y ago
It's tricky, because it's difficult to separate the things we remember with a feeling of nostalgia but that do not really matter from the things that were genuinely useful.
I keep wanting to build some libraries and tools to experiment with this, but a lot of it is about culture, as I mentioned, which is often harder than the tech.
One simple example is the AmigaOS ReadArgs() call. It provides a standard mechanism for parsing command lines. An important consequence of it is that auto-complete for Amiga terminals that supports it can do typed auto-complete for any application that uses it without anyone having to write auto-complete script or specifications.
It's not a hard thing to do. The ReadArgs templates are really basic. Probably too basic. There are tons of good open-source command line parsers. All that's really needed is for people to settle on one with a suitable static spec format, and a mechanism for making it easy to extract that format from an executable.
But it serves very little purpose unless you convince a lot of people to do it.
There's a chicken and egg scenario there, in that it's a lot harder to find people prepared to spend time creating "standards" like that and pushing them than it is to find people to work on solving an issue with a more immediate payoff. Especially when you really need a critical mass of applications that supports these specs before the benefits starts becoming obvious.