The Weakness of the .NET OSS Ecosystem • Hacker News Board

Re: The Weakness of the .NET OSS Ecosystem

#211

Post by mistermann » Sun, Jul 26, 2015, 6:44 AM UTC

tacos wrote: post #40

vdnkh wrote: 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…

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…

> when I can write three lines of code in a version of F# that shipped six years ago and issue SQL-like data gathering queries over everything from Wikipedia to the Department of Labor.

What's the name this technology goes by, and is it possible in C# (regardless of if it's extra lines of code)?

Re: The Weakness of the .NET OSS Ecosystem

#212

Post by mistermann » Sun, Jul 26, 2015, 6:54 AM UTC

manigandham wrote: post #204

eropple wrote: post #188

Earlier quoted context omitted.

Here's the thing: literally none of that is right. You had to assume a lot of facts not in evidence to be that much of a jerk. It was a big task. But you did it! - Almost every developer was converted to .NET to work there, because Microsoft's credibility among startup-focused developers is not great outside of a few specific tools like SQL Server. It's a lot easier to get enough hands to get the job done when you le…

Specific question: What kind of load needs scaling within seconds? If it's so sensitive why not have extra capacity available?

I also wondered that. I think a lot of technical people are irresistibly drawn to solving scale & performance problems by resorting to ever more complex rube goldberg machines & processes rather than just throw a few measly grand of hardware at it and be done.

Stackoverflow is one example of scale with a pretty boring architecture.

Re: The Weakness of the .NET OSS Ecosystem

#213

Post by brightball » Sun, Jul 26, 2015, 7:30 AM UTC

lenocinor wrote: post #195

dragonwriter wrote: post #184

Earlier quoted context omitted.

They named their framework ASP.Net MVC, as it is an MVC framework for ASP.Net, The naming isn't that problematic. Lots of people in the close-minded cult of Microsoft (which does not include all Microsoft devs.) both shorten the name to "MVC" (which isn't necessarily bad in certain contexts) and have little-to-no understanding of what MVC is other than ASP.Net MVC, so both themselves confuse the pattern with the Micr…

And there's Spring MVC too. It's not like only Microsoft is doing that sort of thing.

Most people just call that Spring or Spring framework though (in my experience).

Re: The Weakness of the .NET OSS Ecosystem

#214

Post by tacos » Tue, Jul 28, 2015, 3:31 PM UTC

mistermann wrote: post #211

tacos wrote: post #40

Earlier 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…

> when I can write three lines of code in a version of F# that shipped six years ago and issue SQL-like data gathering queries over everything from Wikipedia to the Department of Labor. What's the name this technology goes by, and is it possible in C# (regardless of if it's extra lines of code)?

F# type providers. Quick entry point: http://tomasp.net/blog/fsharp-data.aspx/

It's kinda awesome.

C# provides similar (but somehow less fun) stuff via LINQ providers. Search "LINQ to [noun]" and you'll find plenty of open source code.

Re: The Weakness of the .NET OSS Ecosystem

#215

Post by achr2 » Fri, Jul 31, 2015, 8:09 PM UTC

pistle wrote: post #124

achr2 wrote: post #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.

Was AvalonDock one?

Indeed.