51–60 of 188 posts
> 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.
https://www.ibm.com/support/knowledgecenter/en/ssw_aix_72/ge...
not if you look at average consumer patterns (sadly)
Earlier 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.
- are composed of multiple processes; can include process management code
- can access hardware directly (for efficient arrangement, caching and retrieval of data)
- include support for multiple users, concurrent sessions
- stored procedures require compiler tooling and runtime (VM)
- can be platform-independent, with an abstraction layer connecting them to the underlying OS
I want linux with:
— Wayland
— KDE and only KDE
— Development SDK based on Qt (other toolkits strongly restricted, gtk and gnome gone wrong way)
— Packaging based on something like APK from android or like DMG (no repos by default, only for base system maybe, but other methods of installing not restricted).
Snaps and flatpack are trash because their goal is so called security and isolation, when normal human being need just convenience (hate repos on desktop).
Yes, it's macOS model, but with linux you can have different filesystems.
> A dream of an ultimate OS I want linux with: — Wayland — KDE and only KDE — Development SDK based on Qt (other toolkits strongly restricted, gtk and gnome gone wrong way) — Packaging based on something like APK from android or like DMG (no repos by default, only for base system maybe, but other methods of installing not restricted). Snaps and flatpack are trash because their goal is so called security and isolation…
You could certainly make a distribution in which using anything but Qt would be very very difficult. But who would want to use such a thing? Besides you, of course.
Moreover, your comment isn’t a cogent response to the post. Did you even read it? He’s talking about a new paradigm of OS, something fundamentally different. What you’re talking about is the same old same old, but worse.
> 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…
So Plan 9, then? But maybe with a database like interface instead of a file like one.
> The hierarchical organization of file systems manifests itself in nesting of directories (folders). On the other hand, directories are merely named views of a certain subset of files, selected according to some criteria. Thus, a directory can be thought of as a "database view," a named database query. It follows immediately that a file may appear in as many "directories" (views) as one wishes to. For example, one "folder" may show all files tagged as "sales reports", while another directory contains files modified within five days. Searching a file system and creating and populating a folder becomes therefore the same activity. Since saved views are database objects themselves, one can reference views within views if one so wishes. There is no required hierarchy however: one may create two views that refer to each other, or any other network of views that best suits the problem.
I built koios to solve this problem, but I didn't take the fuse approach because it seemed like a lot of extra work for the user, and puts databases first rather than files, which is un-UNIX.
> A dream of an ultimate OS I want linux with: — Wayland — KDE and only KDE — Development SDK based on Qt (other toolkits strongly restricted, gtk and gnome gone wrong way) — Packaging based on something like APK from android or like DMG (no repos by default, only for base system maybe, but other methods of installing not restricted). Snaps and flatpack are trash because their goal is so called security and isolation…
I don’t think very many people agree with you. I appreciate Unix/Linux because they are fundamentally libertarian. I don’t have to suffer using some default crappy and bloated desktop environment (KDE certainly fits that definition), I get to choose (I personally like cwm). You could certainly make a distribution in which using anything but Qt would be very very difficult. But who would want to use such a thing? Besi…