Hi Derek,

Derek Hohls schrieb:

[…]

I agree from a *marketing* perspective that putting buzzwords on your site is a way to attract new users - especially those who might otherwise be going to .NET or Ruby-on-Rails - not that I mean to imply the developers are doing this for that reason alone. However, there is also such a thing as a "legacy" application; while you (or others) might think that languages such as COBOL, FORTRAN, Pascal etc are "dead", I can almost guarantee you there are millions of lines of code in those tools being written or maintained every year (C# notwithstanding). There are many of us who have been using Cocoon for many years now, and I would really hate to think we'll just be dumped because some new ideas or support frameworks have emerged.

do you have the feeling that the 2.1 branch is not sufficiently supported anymore? If I understand Betrand correctly, it is officially in maintenance mode and it is not planned to cease support. We (the Lenya community) are certainly going to need it for another couple of years, so we'll be bound to maintain it.


Personally, I'd also like to see the documentation develop and
mature a little more - there are certainly *lots* of "getting started"
questions in the ML about 2.2 - and a book or half would also provide some reassurance that a solid new ship is ready for all
types of sailors.

+1

So yes, I am prepared to learn - no doubt I will have to - but it
does not yet feel the right time for what appears to require a significant upheaval.

Sorry if my mail caused any offence or could be taken personally, that was not my intention. I only wanted to express the viewpoint of another type of Cocoon user – the projects which depend on it.

Thanks for your reply!

-- Andreas


--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org

Reply via email to