﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>Belvasis,
  
NHibernate is over 6 years old, Castle is over 5 years.
  
I would make the claim that they are much better supported than the other options.
  
All you have to do is remind them of L2S fate.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment19</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment19</guid><pubDate>Sun, 31 May 2009 15:01:00 GMT</pubDate></item><item><title>Belvasis commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>Ayende,
  
you are right and we share the same opinion on that. What i wrote was form the perspective of the "managers". Right now I make some preliminary considerations about how our new application should be done. I want to use NHibernate and Castle but have to convince my bosses and they come up with the above arguments. Since they have poor technical knowledge it's hard  to explain to them why it makes no sense to build an own DAL or why EF is n't a real alternative solution.
  
"It is from MS so it has to be good and will be good supported over the years"...this is the point where i have to come up with some good (nont technical) arguments :-)
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment18</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment18</guid><pubDate>Sun, 31 May 2009 11:16:09 GMT</pubDate></item><item><title>Ayende Rahien commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>Belvasis,
  
First, I could point out quite a few commercial products that are now gone. And with OSS, you have the insurance policy of having the source. You can _pay_ people to work on that. Usually, the project owners would be delighted to do so.
  
That is much harder to do with commercial software.
  
In addition to that, there _are_ commercial support avenues for both Castle and NHibernate.
  
Castle Strong and Hibernating Rhinos are both companies that will offer commercial support for either.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment17</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment17</guid><pubDate>Sun, 31 May 2009 05:16:40 GMT</pubDate></item><item><title>belvasis commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>"And from the Open Source perspective, things are looking quite good"
  
...yes i think this is surely true, but nobody talks about the possible 
  
risks arising using OSS in real projects. Who knows how long the 
  
contributors are be willing or be able to commit to the OSS? This is often an existential question for a company developing applications that must be sold over a couple of years. So you have to trust in continuous bug fixing and support. Sure you have the sources and could do it by yourself, but can a small or medium company offer the time frame and man power to afford  this, mainly if the most employees have just moderate skills and are no Ayendes, Fabios, Krzysztof to name just a few? 
  
Take GENTLE.NET for example. Years ago this was one of the ORM's 
  
the .NET world talked about. And today...it's gone. Beside this, one 
  
other problem case is documentation and support. In most cases the 
  
documentations are pretty poor and good examples are missing. So 
  
one has to invest hours and hours to google around the web to find 
  
an answer or even a clue to solve one little problem. Sure you can 
  
use the mailing lists, but even there it is mostly hard to get an answer.
  
So in my opinion these are some problems with OSS that leads 
  
companies to take up the position "if it's not the blessed Microsoft 
  
solution, it's not to be used in projects". I think this is a great pity, but 
  
somehow understandable. NHibernate and Castle are both great 
  
projects in technical terms. So why not for instance offering some 
  
commercial support for NHibernate or Castle? That would spread the 
  
word and could appease the decision makers...
  
So now I hope I will not be killed :-)
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment16</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment16</guid><pubDate>Sat, 30 May 2009 23:54:53 GMT</pubDate></item><item><title>reddeteriterator commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>It's a shame that MS will screw the .Net platform in a few years to force companies to upgrade and all your work will be forgotten.
  
  
  
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment15</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment15</guid><pubDate>Sun, 24 May 2009 02:27:56 GMT</pubDate></item><item><title>Tom Willis commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>I still come across several companies with the attitude that if it's not the blessed Microsoft solution, it's not to be used in projects. Which is why even in 2009, I'm forced to write a data access layer. Maybe it varies greatly by industry or region.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment14</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment14</guid><pubDate>Fri, 22 May 2009 13:52:28 GMT</pubDate></item><item><title>Torkel commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>Good post!
  
  
The trend is definitely promising. Especially if you consider Microsofts small but significant step in supporting open source via jquery partnership.  
  
  
But sometimes i can't help but wish it was going faster, there are still large islands where the misconceptions about open source still prevail. 
  
  
And i am still waiting for Microsoft to support an open source .NET framework  / tool instead of making their own (MSTest, MSBuild, ASP.NET MVC, TFS Build Server, Entity Framework, etc). 
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment13</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment13</guid><pubDate>Fri, 22 May 2009 07:24:08 GMT</pubDate></item><item><title>Nathan commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>&gt; As that confusion has gone away with better understanding we are starting to see more of an embrace of Open Source.
  
  
No, we're seeing am embrace of Free Software. Things that are open source like Microsoft's various "Shared Source" initiatives but which are not Free Software have been largely ignored.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment12</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment12</guid><pubDate>Thu, 21 May 2009 22:09:40 GMT</pubDate></item><item><title>Jason Y commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>Because duplicating software is basically free, there is an economic paradox at work: While it seems crazy at first to release code for free, it becomes clear under closer evaluation that sharing code openly is to one's own benefit in many cases.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment11</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment11</guid><pubDate>Thu, 21 May 2009 17:17:00 GMT</pubDate></item><item><title>Chris Cyvas commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>One other thing to note is that dashCommerce has just been awarded a US Government contract, which means that dashCommerce will be used by the US Government. IMHO, this is a huge win for OSS - especially .NET based OSS.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment10</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment10</guid><pubDate>Thu, 21 May 2009 13:23:49 GMT</pubDate></item><item><title>zvolkov commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>Your link is broken: 
[http://manning.org/rahien](http://manning.org/rahien)</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment9</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment9</guid><pubDate>Thu, 21 May 2009 12:37:40 GMT</pubDate></item><item><title>j23tom commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>@Jozef Sevcik
  
...and finally  they join you (vide all MS-pl'ed projects like Silverlight tools, DLR etc)
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment8</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment8</guid><pubDate>Thu, 21 May 2009 11:18:12 GMT</pubDate></item><item><title>Jozef Sevcik commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>"Open source was considered a threat and Steve Balmer was busy blasting at any OSS project that showed up."
  
First they ignore you, then they laugh at you, then they fight you, then you win. -  Mahatma Gandhi
  
  
Thanks for all the hard work.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment7</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment7</guid><pubDate>Thu, 21 May 2009 08:26:17 GMT</pubDate></item><item><title>Ken Egozi commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>@  Nicholas Piasecki: you got to be kidding, right?
  
  
Monorail had *one* major "breaking change" during its lifetime. 
  
I say "braking change" because the change was in the API, not in the behaviour. thus a couple of hours of search-and-replace is all one needed to migrate.
  
On top of that, the introduction of IController and breaking up the Contexts was a huge effort, and a super important one. It was a significant improvement in the design, and allowed further changes and upgrades to be more easy, improved the testing ability thus made MR even more stable.
  
  
Now you stayed on the ancient RC2 for a *very* long time, and even though everyone involved in the project has always promoted the use of trunk, you just jumped ahead to do so in 2009 - about three years after.
  
  
This reminds me of people implementing Data Access in .NET, and trying to "improve" things by reusing IDbConnections and passing them around. then connections start to leak, then their DB hangs, then they blame ADO.NET.  they simply ignore the best-practice that is given by the ADO.NET team (trust connection pooling - do not reuse IdnbConnections), then whine.
  
  
So - if you don't follow the best practices of the creators, please don't whine about it.
  
  
I've been a user of Monorail for almost four years now. Always for *real* code that goes to production. On many projects. And I followed the best practices of the team, and had a pleasure using that. That was way *before* I became part of the team, and is actually the reason I started contributing in the first place.
  
  
  
In a way I'm sorry for the rant, however what pissed me off was your saying on "unnecessary ways". Dude - it *was* necessary. If you don't like it - you can either stay on RC2, or come up with better patches,  That's OSS.
  
And if you have a problem with the release cycle and wants to see MR2.0 RTM, you can always contact me and offer your help with that. 
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment6</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment6</guid><pubDate>Thu, 21 May 2009 05:50:15 GMT</pubDate></item><item><title>FallenGameR commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>There are some mature OSS projects like Spring.NET and log4net that have been around for years.
  
  
One the other hand we have Microsoft Enterprise Library that is significantly changed once per year.
  
  
After this post I incline to think that it's better to learn log4net rather then logging with Enterprise Library.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment5</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment5</guid><pubDate>Wed, 20 May 2009 23:05:54 GMT</pubDate></item><item><title>Patrick McEvoy commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>And then there's Mono...
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment4</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment4</guid><pubDate>Wed, 20 May 2009 22:52:44 GMT</pubDate></item><item><title>Andrea Balducci commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>I totally agree wiith you. I've started to share my code with the community and to support .Net Communities actively. Three years ago I was working in a company where open source was seen as smoke in eyes. Now i run my own company and I'm thinking about opening all my code... there's no need to reinvent the wheel, it's better join an open source project and spend our efforts to build great software instead building all from scratch or porting every 2 years. 
  
My first .Net project was using NHibernate and still today. Never used another data access layer up to now...
  
tnx.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment3</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment3</guid><pubDate>Wed, 20 May 2009 22:28:56 GMT</pubDate></item><item><title>Nicholas Piasecki commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>Good points, but I would argue that Castle (well, MonoRail in particular) has been far from "stable"--interfaces and inheritance contracts have been broken in "release candidates" in 
[many unnecessary ways](http://groups.google.com/group/castle-project-users/browse_thread/thread/0ea39fd784720bb1).
  
  
That said, without these open source projects, I doubt things like ASP.NET MVC, MSTest (maligned that it may be) in the Professional edition of Visual Studio, or Entity Framework would have happened when they did. So let's keep on trucking.
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment2</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment2</guid><pubDate>Wed, 20 May 2009 21:52:13 GMT</pubDate></item><item><title>Steve Sheldon commented on The state of Open Source in the .NET ecosystem: A five year summary</title><description>Much of the debate has been confused by the difference between Open Source and Free Software.  The opposition really has had to do with the GPL, and unfortunately both sides of the debate confused Open Source with that particular license.  The GPL proponents purposefully, and the opponents because they were confused.  As that confusion has gone away with better understanding we are starting to see more of an embrace of Open Source.
  
  
That being said, the client I work for still won't touch open source.  The reason is they have big corporate clients and when these clients send them security questionnaires there is a question on there "Does your software use Open Source?".  So out of fear they avoid the question. 
</description><link>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment1</link><guid>http://ayende.com/4026/the-state-of-open-source-in-the-net-ecosystem-a-five-year-summary#comment1</guid><pubDate>Wed, 20 May 2009 21:50:41 GMT</pubDate></item></channel></rss>