> On 7 Nov 2016, at 10:42, Norbert Hartl <norb...@hartl.name> wrote: > >> >> Am 07.11.2016 um 10:28 schrieb Esteban Lorenzano <esteba...@gmail.com>: >> >> >>> On 7 Nov 2016, at 10:17, Sven Van Caekenberghe <s...@stfx.eu> wrote: >>> >>> >>>> On 7 Nov 2016, at 10:13, Thierry Goubier <thierry.goub...@gmail.com> wrote: >>>> >>>> I've seen over the years many, many attempts at replacing the filetree >>>> format. I used to contest and debate, now I just let them go and die a few >>>> months later. Because none of the alternatives are clearly superior, and >>>> it is not worth the effort to reimplement. >>>> >>>> (I quite enjoy reading filetree-based code on github: it is layed out like >>>> my browser, neat and clean. Moreover, all my code involve multiple >>>> classes, which means switching between files anyway. Given that reading >>>> those !! was never a pleasure, even when I started using Smalltalk in 1991) >>> >>> Indeed. I agree 100%. >> >> I was even thinking on propose someone (a student project, maybe?) to do an >> embeddable browser people could put in their README.md, to browse sources >> “as in Pharo” :) >> a Seaside app to do that would not be hard, I think… and can be hosted on >> PharoCloud (or whatever you want). >> > I fully agree to your previous mail (the long one) but want to add that it is > not only the number of things to maintain that plays an important role in > taming complexity. You can count the complexity of each project into that > calculation. And proposing something using seaside is not an approach > according to this rule ;)
I know :) I’m not saying I will do it… or maintain it… just that it would be cool and fairly easy :P Esteban > > Norbert
