Well, I like the idea of the massive refactoring for two reasons: 1) There's a lot in the core that still uses the .NET v1.1 non-generic collections. It gives the impression that its "old-fashioned", which is not the feel we want for a "Cutting edge" alternate to ASP.NET.
2) There are a lot of loose-ends, and half-done features in there -- When I was working on adding Portable Areas, I discovered that 90% of the most difficult part was already in the core --- it just was being used to anything. Truth, James 2010/7/14 Henry Conceição <[email protected]>: > On the roadmap 2.1 thread, John asked me: > > "Actually, it would be nice to hear your thoughts on the future of MR? > The way I see it, MS MVC2 has pretty much caught up with MR features > and the way things are going MS MVC3 is pretty much going to blow MR > out of the water, so if we don't do massive refactoring and > improvements, what should we do?" > > I think refactoring the current implementation and try to offer > similar and/or slightly better implemented features won't be enough. > Or Monorail 3 turn out to be something really innovative on the .Net > land or it'll be remembered only as the hippie alternative for that ms > web framework. Companies and/or people won't buy the risk of trust on > us or go against the status quo for such small reward. > > Do I have an awesome ideia to it? Unfortunately no. Just a few sparse > thoughts of what Dlr, Conventions, Composition and a more intelligent > view engine could do, but nothing concrete. -- 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.
