Although ext3cow has revision history, it probably has no change propagation. Revision control systems (like CVS or Subversion) must have both. Change propagation is needed to keep everyone in sync. So you'd have to add a tool for that.
That's the beauty of a file system, though. You can accomplish anything just by adding new tools on top. Instead of marrying tool functions (like revision control) to the file system, you keep them separate. The big advantage being that you can choose them independently, and mix and match (there being many file systems to choose from,
and many revision control systems). In this sense, maybe ext3cow is a step in the wrong direction?
"To be sure, ext3cow is not the first versioning file system...
VMS, TOPS, CedarFS, FFS, Elephant, LFS, CVFS, AndrewFS, WAFL,
SnapFS, Venti, Spiralog, Plan-9, Wayback, VersionFS..." (FAQ).
To most of us it sounds like a new idea, but it's not. It just never caught on. I wonder if the reason is, at least partly, that revision control belongs in a separate tool?
Slashdot Mirror
That article is misleading. It has nothing to do with AJAX,
a nguage.html
s t-impressions-suns-javafx-platform-for-rich-applic ation-development.html/ sun_javafx.cfm
and nothing to do with the Web.
It's basically JavaFX Script, a language for defining GUI's.
https://openjfx.dev.java.net/JavaFX_Programming_L
These are better articles:
http://arstechnica.com/news.ars/post/20070509-fir
http://weblogs.macromedia.com/jd/archives/2007/05
-- Mike
Although ext3cow has revision history, it probably has no change propagation.
Revision control systems (like CVS or Subversion) must have both.
Change propagation is needed to keep everyone in sync.
So you'd have to add a tool for that.
That's the beauty of a file system, though.
You can accomplish anything just by adding new tools on top.
Instead of marrying tool functions (like revision control) to the file system,
you keep them separate. The big advantage being
that you can choose them independently, and mix and match
(there being many file systems to choose from,
and many revision control systems).
In this sense, maybe ext3cow is a step in the wrong direction?
"To be sure, ext3cow is not the first versioning file system...
VMS, TOPS, CedarFS, FFS, Elephant, LFS, CVFS, AndrewFS, WAFL,
SnapFS, Venti, Spiralog, Plan-9, Wayback, VersionFS..." (FAQ).
To most of us it sounds like a new idea, but it's not.
It just never caught on. I wonder if the reason is, at least partly,
that revision control belongs in a separate tool?