Live data from Hacker News

The Weakness of the .NET OSS Ecosystem

aaronstannard.com

21–30 of 215 posts

Re: The Weakness of the .NET OSS Ecosystem

#21
post #17

Yes, the author is correct. There is a distinct lack of OSS in .NET. I've been trying to find a project to contribute to among the graveyard on Github. However, I think the author falls flat explaining the why. I have a few thory on this. For so long C# has been a walled garden of closed source software. This closed source software, for the most part, works damn well. Why reinvent a square wheel when there is a shop…

Agreed.

Re: The Weakness of the .NET OSS Ecosystem

#22
A 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 to drive them.

Re: The Weakness of the .NET OSS Ecosystem

#23
post #4

Alternate title: "It's hard to build a church on top of a native american burial ground."

I liked this analogy. Why is it getting downvoted? It's totally true. Too much cognitive dissonance between open-source on a for-profit foundation.

Tons of open source software is developed by for profit companies???

Re: The Weakness of the .NET OSS Ecosystem

#24
post #17

Yes, the author is correct. There is a distinct lack of OSS in .NET. I've been trying to find a project to contribute to among the graveyard on Github. However, I think the author falls flat explaining the why. I have a few thory on this. For so long C# has been a walled garden of closed source software. This closed source software, for the most part, works damn well. Why reinvent a square wheel when there is a shop…

I think there's definitely something to this.

Another that I think makes a big difference is that Microsoft has historically charged money for reasonably featureful versions of their dev tools. I think it leads a lot of people who work in .NET during the day to do hobby work on some other platform. The freely available dev tools for Ruby might not be any more featureful than Visual Studio Express, but the simple fact that you're working on a different platform from the one where you get to work with all these high-end power tools during the day means you notice that difference less.

Hopefully the new Community Edition will change that that situation.

Re: The Weakness of the .NET OSS Ecosystem

#26
post #23

Earlier quoted context omitted.

I liked this analogy. Why is it getting downvoted? It's totally true. Too much cognitive dissonance between open-source on a for-profit foundation.

Tons of open source software is developed by for profit companies???

Not so much where the profit comes from selling software.

If Microsoft open sourced Windows and Office they would instantly stop making money, hence they will always have an uncomfortable relationship with open source.

Re: The Weakness of the .NET OSS Ecosystem

#27
I asked on Twitter long ago for any prominent examples of open source software that originated on Windows and transitioned to other platforms. I think after some discussion we may have come up with an example. Maybe. I certainly can't recall what it was.

Re: The Weakness of the .NET OSS Ecosystem

#28

I asked on Twitter long ago for any prominent examples of open source software that originated on Windows and transitioned to other platforms. I think after some discussion we may have come up with an example. Maybe. I certainly can't recall what it was.

And to the other extreme, I know of quite a few open source projects on .NET that have gone proprietary. ServiceStack anyone? Kinda leaves a little bit of a bitter taste in the mouth.

Re: The Weakness of the .NET OSS Ecosystem

#29
This is a real problem. Not one, but two great open source WPF control libraries I contributed to got 'taken over' (bought out I assume) by a major component seller (XCEED). Of course the community contributions disappeared as the company started selling updates as a pro version with their 'premium' features.

Re: The Weakness of the .NET OSS Ecosystem

#30
post #6

The OSS "weaknesses" of .net are a chicken and an egg problem; the more people who come from a community software background that use a framework, the more community software there will be for that framework. Having what reads as a very angry and negative blogpost about the state of .net oss isn't really helping. Contributing software is though, and that really should have been the focus of the post, not how weak and…

> Be the change you seek He is: https://petabridge.com/about/

I wasn't saying he hadn't, in fact right above that line I acknowledged that he had. This is more for .net devs generally.
Post reply on HN