Re: reiser4?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: reiser4?
by Evan "JabberWokky" E. on Wednesday 23/Feb/2005, @14:12

:: One could argue that this is where the information belongs: in the filesystem.

The problem is, KDE targets the nebulous "Unix" as a goal. POSIX does not define much (are ACLs even defined as a standard, or are they an optional part of the standard?).

:: IIRC, Hans Reiser said that whenever you use a database, its because of the shortcomings of your filesystem, and the now-released reiser4 is supposed to fix that.

I agree so wholeheartedly it is difficult to express with words. I think a rich filesystem that is used by apps is as revolutionary as the desktop metaphor. But I also think that KDE is right not to make such a fundamental requirement. As an *optional* way of storing data, on the other hand...

Not to mention that a rich filesystem plus an advanced code rights system (a la jail) will result in a very secure, powerful and stable system - far more abuse tolerant and flexible than has ever been commonly available ("Open all the attachments you want - they run fine, anything they change rolls back, and they can't send Spam").

Related Links

·   Articles on Community and Events
·   Also by Evan "JabberWokky" E.
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: reiser4?
by Aaron J. Seigo on Wednesday 23/Feb/2005, @15:44

> I think a rich filesystem that is used by apps

you hit the nail on the head: it has to be used by applications. if no applications use it, it's a theoretically cool idea with no real world benefits and becomes an unimportant interesting footnote in computing history.

this is why instead of targeting a unique storage system or creating one application/tool, we're creating a system that will allow any (and hopefully as close to "all" as possible) application to easily take advantage of these paradigms.

the location of the storage, filesystem or database or clay tablet, is an implementation detail with implications for performance and ease of implementation only. it's the application APIs that matter, and which are also missing. to analogize, Reiser and RDBMS's are like X Window: low level technologies that provides a means to accomplish the task (with varying degrees of success); things like what this interview is about are like Qt: a layer that makes application development leveraging the possibilities of the platforms possible.

innovation is not just the creation of a new idea, it's the implementation of that new idea in the marketplace.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I never sing because it upsets our dogs." -- Waldo Bastian
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.