4 ms·
Seeing it from the perspective of a network filesystem (WebDAV by itself is a lot more, albeit afaik has never been used seriously as an authoring tool) it is a
by unbit 12y ago
Seeing it from the perspective of a network filesystem (WebDAV by itself is a lot more, albeit afaik has never been used seriously as an authoring tool) it is a bit over-engineered, but the real problem (expecially when dealing with CardDAV and CalDAV) is the clients/servers inter-operation, as it looks like no-one is able to respect the RFCs (check the amount of hacks the radicale project or davvy needed to make OSX clients happy, or the differences between lightning, korganizer and so on). So the reason is that my patience ended :)
- deleted 12y ago[deleted]
- unbit 12y agolol :) but as already said there is no standard for POSIX access via HTTP. (WebDAV is not a competitor here, it is only the cause that pushed the development of spockfs)
- Lerc 12y agoI'm wondering if Randall regrets writing this one because of the frequency it gets cited as a argument against new standards. Almost every commonly used Standard was born in a world with existing standards purporting to be the ideal solution for that niche. It's not even the sentiment that the comic represents. The comic refers to standards that try to in-the-darkness-bind-them. Competing formats and protocols should be encouraged and should compete on merit. If people use them because they are good, _then_ they can be elevated to the status of a standard. Bad formats only proliferate when they have another driving force behind them. "It's the standard" is one of those driving forces. Proprietary (and Cathedral) software also have the "We made this and you have to use it" problem.