> But it does not have to be this way. If a database engine is implemented as a core system service, along with simple tools to browse and modify database records, the gordian knot of system configuration files disappears. MacOS comes very close to this ideal, with ResEdit as this universal database editor. Or AS/400, which is more or less a SQL database.
I used to work with an AS/400, and never once thought of it as a database - sure, it had DB2 pre-installed, but I don't see how that makes the OS itself a database?
A dream of an ultimate OS (1995)
31–40 of 188 posts
Re: A dream of an ultimate OS (1995)
#32> But it does not have to be this way. If a database engine is implemented as a core system service, along with simple tools to browse and modify database records, the gordian knot of system configuration files disappears. MacOS comes very close to this ideal, with ResEdit as this universal database editor. Or AS/400, which is more or less a SQL database.
> Or AS/400, which is more or less a SQL database. People keep on saying that, but how really true is it? Many operating systems come with bundled relational databases–e.g. most Linux distributions come with more than one relational database implementation bundled. Does that make Linux "more or less a SQL database"? How deeply integrated is DB2/400 into the OS/400 kernel (or equivalent term, such as "System Licensed…
Re: A dream of an ultimate OS (1995)
#33Re: A dream of an ultimate OS (1995)
#34Earlier quoted context omitted.
> Or AS/400, which is more or less a SQL database. People keep on saying that, but how really true is it? Many operating systems come with bundled relational databases–e.g. most Linux distributions come with more than one relational database implementation bundled. Does that make Linux "more or less a SQL database"? How deeply integrated is DB2/400 into the OS/400 kernel (or equivalent term, such as "System Licensed…
People who used it characterized it that way.
Re: A dream of an ultimate OS (1995)
#35It's not clear whether the author is arguing that all existing OS data structures should be replaced with a single database system, or if they simply want all OS data to be capable of being queried/updated via a standard database style interface.
The former is simply hubris ("I know the perfect data structure for EVERYTHING!") while the latter is pretty much implementable as an interface layer on top of an existing OS.
Re: A dream of an ultimate OS (1995)
#36Re: A dream of an ultimate OS (1995)
#37At "ultimate", I thought the author was going to aim for consciousness... But what, databases?!
It uses soup unions to manage removable storage, and worked really well for the 512k memory available.
These days I'd recommend an embedded SQLite database for program configuration and data - somewhat standard, easily recoverable, backups are easy, uniform access from a program's API etc.
Lastly, I'd say the ultimate OS would have a bit more than this surely - minimal formally verified TCB, Arrow datastructures, Managed (but not GC'd) memory, native scripting language that blurs the distinction between users and developers, fully scalable auto-generative but skinnable UI, just to name a few.
I guess the trick with all of this is a suitable language which forms the OS base (think LISP OSes, Micropython, Squeak, AOS, NewtonOS), you get that correct and the rest can be layered on top.
Re: A dream of an ultimate OS (1995)
#38Earlier quoted context omitted.
People who used it characterized it that way.
I know they did/do. But when they characterise it that way, are they just repeating IBM marketing assertions without challenging them?
Re: A dream of an ultimate OS (1995)
#39Earlier quoted context omitted.
Actually Microsoft tried this idea themselves with WinFS. It was planned for Vista but eventually the project was stopped because it was too much effort. I could imagine this to be really useful if it was possible to add arbitrary custom attributes.
Does anyone have the story on why this project was actually halted? It reportedly sounded like it would have been a giant leap at the time, had it actually landed.
Re: A dream of an ultimate OS (1995)
#40Why not to trade a multitude of "custom" database managers for a single well-designed distributed database manager? It's not clear whether the author is arguing that all existing OS data structures should be replaced with a single database system, or if they simply want all OS data to be capable of being queried/updated via a standard database style interface. The former is simply hubris ("I know the perfect data str…
For more info check https://www.researchgate.net/publication/2364452_Data_Struct...