Good stuff, Jan. One thing that bites 'technologists' like us is thinking too much in the terms of features disregarding the whole end-to-end story. asp.net mvc, to give an obvious example, has less features than MonoRail, but has a great end-to-end story including a nice VS integration.
One thing to use to avoid this pitfall is to have every feature suggestion being backed up by at least three reasonable scenarios. Another thing is listing the whole pain points associated with a technology, an prioritize them. For MR, routing and creating a project seems to be the bigger ones. I can keep rambling on and on, but that's the essence of it. Just two cents. On Mon, Mar 15, 2010 at 7:26 PM, Jan Limpens <[email protected]> wrote: > From my point of view, I hope nobody minds my late involvement in this > discussion, MR's future should concentrate less in features and more > in architecture. -- Cheers, hammett http://hammett.castleproject.org/ -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
