In regards to the new vs project creation schema, I just read this blogpost: http://devlicio.us/blogs/rob_reynolds/archive/2010/02/01/warmup-getting-started.aspx Sound just like the thing - backed via a hornget build (with some architecture in place everybody can agree upon, maybe some switch for the desired view engine), people could just get the newest builds, tested and working well together from some castle build server.
In regards to FOSS and MS - things are changing, too. Nobody would have guessed that MS ever would release sources for anything at all or just use a FOSS project, JQuery, as it's mainly supported js engine (even having something similar not all that bad ready). There is a huge contrib movement towards mvc, that is entirely in community hands. We .netties have the luxury of having somebody bank the development of a huge framework that encompasses 80% of everything needed. Java, phytonists etc.. have to take care of themselves quite a lot more. With both good and bad consequences... On Wed, Mar 17, 2010 at 11:57 AM, Stuart <[email protected]> wrote: > On Mar 16, 10:27 pm, Jan Limpens <[email protected]> wrote: >> >> Soon >> (next release, or the one after that) asp.net mvc will be better than >> the current mr in almost every aspect and has a huge community behind >> it. It would not be a good decision to place your bets on a small foss >> project, if there is another version of the same backed by the biggest >> player in the marked, community behind it, almost open sourced, >> extensible, etc... >> >> So, I think, if MR does not want to carry the [Obsolete] attribute, it >> will have to evolve radically. >> > > May I say something likely to be unpopular? The .Net ecosystem is anti- > FOSS. For all the talk championing open source over the past couple > years, we can clearly see from the example of the MonoRail project > that .Net developers prefer proprietary software. They will use an > open source project only insofar as there is no alternative solution > from Microsoft. Meanwhile we will continue to see MSFT crank out > 'official' solutions to compete with any sufficiently popular open > source project. > > I've had the privilege of working completely outside the .Net > ecosystem for the past several months, using python, django, > postgresql, debian, etc. I'm spoiled. As freeing as working with the > Castle Project and NHibernate felt when I was coming from > 'traditional' .Net development, I have to say that my present > experience with FOSS -- pure FOSS -- is a thousand times more freeing. > > I love the Castle Project. If 'they' ever make me go back to Visual > Studio, Windows, and .Net, then MonoRail + Windsor et. al. will > continue to be my first-choice technology for buildling web apps. I > hope that you guys will be able to keep this project around and > thriving. You have an uphill battle in front of you. It shouldn't be > that way, but it is. > > > --Stuart > > -- > 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. > > -- Jan -- 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.
