When you invent the next format, keep in mind that cross-platform source code sharing is something to consider as well ... It's always harder to make cross-platform code and some compromises have to be made to accommodate multiple dialects ...
Also consider that with FileTree we are only on the first step of Make it work, Make it right, Make it fast ... Put your energy into implementations not arguments:) Dale On Thu, Mar 6, 2014 at 3:09 PM, Esteban A. Maringolo <[email protected]>wrote: > I'm coming late to this, but Dolphin's VCS format has one file per package > and "extensions", and one file per class (instance and metaclass). > > We succesfuly used that approach with git for more than a year. I know > Object Arts did the same but backed by MS VCS (sourcesafe). > > It is good that we're discussing HOW to version everything with an > external file based VCS. That means we'll end up doing it the best possible > way. > > Regards. > El mar 6, 2014 7:51 PM, "Jan Vrany" <[email protected]> escribió: > > On 06/03/14 22:34, Dale Henrichs wrote: >> >>> My dream has finally come true ... Smalltalkers arguing the merits of >>> git vs. mercurial! >>> >> >> Lucky you, I still have to wait for this to happen :-) >> >> Let's make myself clear, +1 was not because of mercurial, >> but because of class-per-file on-disk layout. >> >> Jan >> >> >> >>> Alternate implementations to FileTree are welcome! >>> >>> Dale >>> >>> >>> On Thu, Mar 6, 2014 at 2:06 PM, Jan Vrany <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> >>> >>> The integration in Newspeak is quite different. It is file >>> based, above >>> mercurial (which makes no difference) but the tools one uses are >>> in >>> Newspeak. So mercurial really is just a back-end. Given that >>> organizations and alphabetical order of selectors within >>> protocols, >>> classes within categories, etc, keeps things stable I find >>> mercurial >>> diffs are still pretty readable with file-specific command-line >>> or GUI >>> tools. Method-level granularity seems a very poor choice, >>> IMNSHO. >>> >>> >>> +1. >>> In St/X I do exactly the same. Works just fine. >>> >>> Jan >>> >>> >>> >>> >> >>
