Earlier quoted context omitted.
Free on Windows. And only supported on Windows, despite Rotor. That's a fairly non-trivial "hidden" cost.
https://github.com/dotnet/coreclr Windows, OSX, Linux, FreeBSD
The Weakness of the .NET OSS Ecosystem
131–140 of 215 posts
Re: The Weakness of the .NET OSS Ecosystem
#132A good chunk of that is the "invented here syndrome". With EF, WPF, ASP MVC, MEF, etc, plus annual MSBuild conferences, .Net has far more internally-developed ecosystem than Java. Which tends to promote the idea that the MS way is the right way, and if I need something else I must be doing something wrong (or I need to wait till next year). Perhaps MS should just kill off all these frameworks and force the community…
That's one of my favorite things about Microsoft. Whenever they release a framework or a product, there's a tendency to just call it whatever the name of the technology is as if they invented the whole thing. SQL Server - When .NET developers say SQL they mean SQL Server 90% of the time it seems. MVC - MVC4 is a .NET Rails clone. Named MVC as if Microsoft originated the design pattern that was used to clone another f…
RoR did not invent MVC.
MVC (Model, View, Controller) was created by Alan Kay while working at Xerox, when he created SmallTalk and that was back in 1972.
Edit: My apologies to Trygve Reenskaug as it appears he was the one responsible for adding MVC to SmallTalk.
https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93con...
Re: The Weakness of the .NET OSS Ecosystem
#133I've been really trying to go FOSS (or even OSS) with .NET. But the community does not seem to be very open to it. They do upvote, star or otherwise applaud the effor. Yet nobody uses it. Or even makes the effort to try. My experience with the Python community is quite different. People not only accept the work provided, they actually try and use it and give feedback. It feels good to get a pull request improving som…
I work with an entire department of C# developers, and frankly I don't think they care at all about OSS or giving back to the community. It's kind of a bummer, but I've tried to generate enthusiasm around open sourcing some of our components and was met with blank stares. We've been a Microsoft shop from the start and it's obvious.
Re: The Weakness of the .NET OSS Ecosystem
#134I think it is important to realize that the .NET OSS ecosystem is not something that has been around for a long time. In the F# community, it truly started working as an "OSS ecosystem" only a couple of years ago - and the rest of .NET is following - and I'd say it is only starting to really exist now. Although .NET has been around for ages, people are only learning what OSS means and I think the F# community is lead…
Sorry, but that is a nonsense excuse. The (now abandoned) Spring.NET project[1] was started in 2004, not too long after (Java) Spring started. It's easy to criticize Java Spring, but it's a good example of a long-lived successful Open Source project. It's also easy to argue that Spring isn't as useful in .NET as in Java. But I can pull up many, may other examples (the .NET Lucene port etc). My point is that the .NET…
I tried, and couldn't find exact date when Microsoft officially endorsed Newtonsoft.Json as THE way to handle json in .net. But I believe that this happened just last year. Look, in 2011 Scott Hanselman blogged about this library [1] and the comments (esp. the first one) are pretty interesting. Here, .NET tried to solve a problem and community did a better job, and just recently Microsoft recognized it.
Re: The Weakness of the .NET OSS Ecosystem
#135Earlier quoted context omitted.
In general, you're correct about the difference being social, nt one of licencing. You're wrong on one thing: Microsoft's .NET 1.0 CLR and compilers were also free from day one. You never HAD to use VS to develop with .NET, any more than you HAD to use NetBeans or Eclipse to develop with Java.
True, but I shudder at the thought of having to manage msbuild files by hand without the help of Visual Studio.
Re: The Weakness of the .NET OSS Ecosystem
#136Earlier quoted context omitted.
That's one of my favorite things about Microsoft. Whenever they release a framework or a product, there's a tendency to just call it whatever the name of the technology is as if they invented the whole thing. SQL Server - When .NET developers say SQL they mean SQL Server 90% of the time it seems. MVC - MVC4 is a .NET Rails clone. Named MVC as if Microsoft originated the design pattern that was used to clone another f…
>> The MVC as if Microsoft originated the design pattern RoR did not invent MVC. MVC (Model, View, Controller) was created by Alan Kay while working at Xerox, when he created SmallTalk and that was back in 1972. Edit: My apologies to Trygve Reenskaug as it appears he was the one responsible for adding MVC to SmallTalk. https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93con...
Well aware of that. Was pointing out that Microsoft named their framework MVC as if they did.
Re: The Weakness of the .NET OSS Ecosystem
#137Earlier quoted context omitted.
The tools and libraries from Microsoft are so solid that frankly you don't need an entire class of open source projects. I don't need to "contribute" and "socialize" with some Python craziness named after a dolphin (though I did!) because Amazon provides a real .NET SDK for talking to AWS. I don't need to wrestle with three different constantly-patched Ruby image libraries because .NET has been able to load and save…
You're not wrong. People who don't work in "enterprise" or even in small/medium business IT shops will never know it though. However, I think the downvotes are probably a reaction to the hint of attitude which suggests that you're not overzealous about OSS.
As it happens, I like C#, as a mostly-portable language for writing video games because the runtime has been ported almost anywhere I care about. I have a lot of open-source C# stuff in my Github and have been doing open-source C# since about 2007. But as an ecosystem for high-velocity, agile work, it's got problems. Maybe CoreCLR on Linux, once the bugs are well and truly killed, will be an answer, but it's not there yet.
Re: The Weakness of the .NET OSS Ecosystem
#138Really the simple issue has always been the same with MS-platform based OSS; People look to MS to provide the canonical frameworks, tools, and libraries. MS is far more used in corporate environments as a portion of their market, and are more subject to business decision making; much of that focused on RAD / designer tooling. There's a different philosophy in the open source world - python, perl, c - none really have…
PS: Unfortunately, most Fortune 2000 enterprise (ms and non-ms shops) abuse the fuck out of open source and give zero back (time, $ or help). I really think there should be some "community charge" funding model which doesn't make it nakedly for-profit but rewards people that contribute, maintain and support useful code that is widely deployed so they're not completely abused as unpaid crowdslaves.
Re: The Weakness of the .NET OSS Ecosystem
#139I think it is important to realize that the .NET OSS ecosystem is not something that has been around for a long time. In the F# community, it truly started working as an "OSS ecosystem" only a couple of years ago - and the rest of .NET is following - and I'd say it is only starting to really exist now. Although .NET has been around for ages, people are only learning what OSS means and I think the F# community is lead…
Sorry, but that is a nonsense excuse. The (now abandoned) Spring.NET project[1] was started in 2004, not too long after (Java) Spring started. It's easy to criticize Java Spring, but it's a good example of a long-lived successful Open Source project. It's also easy to argue that Spring isn't as useful in .NET as in Java. But I can pull up many, may other examples (the .NET Lucene port etc). My point is that the .NET…
It's been abandoned? (serious question) That really is too bad. It was a solid project used on several .NET projects in which I participated "back in the day."
BTW, I completely agree with your summary point. There appears to be a cultural rejection of .NET OSS projects.
Re: The Weakness of the .NET OSS Ecosystem
#140Earlier quoted context omitted.
>> The MVC as if Microsoft originated the design pattern RoR did not invent MVC. MVC (Model, View, Controller) was created by Alan Kay while working at Xerox, when he created SmallTalk and that was back in 1972. Edit: My apologies to Trygve Reenskaug as it appears he was the one responsible for adding MVC to SmallTalk. https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93con...
>> RoR did not invent MVC. Well aware of that. Was pointing out that Microsoft named their framework MVC as if they did.
You use of the English language is rather confusing.