5 ms·
costs may not be the biggest problem, but what about the freedom to make changes to the source (to fix a bad exploit, add a feature, ...)? I still remember the
by chaostheory 19y ago
costs may not be the biggest problem, but what about the freedom to make changes to the source (to fix a bad exploit, add a feature, ...)? I still remember the telecom, I used to worked for, being burned by them; we had to pay x thousand dollars for a pre-release patch/bug fix for their black box software...
Speed and quality of evolution/innovation is another factor. MS generally doesn't like open source (their sourceforge clone is a start, but really doesn't go far enough.), and it took forever for MS to catch up to open source with LINQ (and polish it). The same goes for their unit testing and ANT-like deployment tool. (Yes, NHibernate and NANT have been there; but MS pretty much snubbed them instead of embracing them.)
At the end of the day the MS copy machine is fast, but not as fast (or good) as the open source movement.
- paulgb 19y ago> it took forever for MS to catch up to open source with LINQ Sorry to go off-topic, but what were they catching up to exactly? I wasn't aware of anything LINQ-like in open source (not that I'm always aware of these things).
- wanorris 19y agoActually, some of Microsoft Research's Haskell experts have done work to take the concepts from LINQ and port them to Haskell, because it's a cool idea that didn't exist there. Taking monadic combinators and applying them to the problem of generalized querying is indeed something that hadn't been done before. There are various slick data access techniques available in open source, but LINQ is not a knockoff of any of them.
- chaostheory 19y agoimho I still feel LINQ is a knockoff and a really late one (years late). to MS's credit LINQ does bring a lot of improvements; mainly in shorter, more concise syntax
- wanorris 19y agoA knockoff of what exactly?
- chaostheory 19y agothe open source stuff (fine - i'm showing my bias against MS with or without good merit) I'm not saying that you can't build anything good / successful with MS products... and there are situations where going MS is a strong advantage (video games)... I'm just curious why ppl would constrain themselves (in both flexibility and financials) when there's alternative tech that's comparable (or better)
- wanorris 19y agoWhich open source stuff -- that's what I mean. I've used ActiveRecord in Rails and a few other open source data access technologies, but nothing I would consider to be a direct precursor to LINQ. There are a lot of things that Microsoft makes that are derivative of open source -- ASP.NET MVC is effectively yet another Rails knockoff, for example. But AFAIK, LINQ is something new and different, which is why I'm genuinely curious what you would consider to be similar to LINQ but predating it.
- chaostheory 19y agoJava world: Hibernate, Ibatis, and so on .NET world: NHibernate - NHibernate came out years before LINQ (though a good bit after Hibernate). It was stable and powerful. Besides NHibernate there were other similar .NET open source projects, but I'm not familiar with them The same thing can be said of NAnt and NUnit