Live data from Hacker News

The Weakness of the .NET OSS Ecosystem

aaronstannard.com

41–50 of 215 posts

Re: The Weakness of the .NET OSS Ecosystem

#41
post #5

The level intellectual laziness is immense. Most of the developers, me included look at Microsoft for guidance than embracing hard problems and solving it for ourselves. This does not mean .net is filled with incompetent programmers but it is full of "unless you pay" programmers.

You mean the "At least I don't have to use Java" developers?

I think he meant the "developing for a locked in and dead ecosystem" developers.

Re: The Weakness of the .NET OSS Ecosystem

#42

I'm glad that Microsoft is absorbing enough young guys who went through college realizing open-source is cool to actually influence their future direction, but based on the entire self-interested history of Microsoft ( https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish or http://www.pcworld.com/article/2901262/microsoft-tightens-wi... or http://techrights.org/2010/09/17/microsoft-management-mocks-... ) and…

Lots of downvotes, but I can relate to what you are saying. 10 years of working in a pro Microsoft organization trying to do PHP and Ruby development showed me that developers and managers alike bought into Microsoft's ideas at the time. Microsoft was good, Microsoft offered support, and open-source was just for hobbyists. 10 years of working with servers that were hostile towards openness, and 10 years of watching Microsoft blatantly steal from open-source and not give back.

Now they're giving back. And that's great. But I was involved with IronRuby. And I will never trust MS and open-source after that all went down. I'm a big fan of Chocolatey.org, and I'm hearing that MS wants to do their own version of that too.

The more things change...

Re: The Weakness of the .NET OSS Ecosystem

#43
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.

Doesn't explain why Java developed a robust OSS ecosystem long before it went open source. Java did benefit from the model Sun set up on J2EE of setting out JSR 'specifications' and only providing limited capability reference implementations, which made it possible for the Apache Java ecosystem to spring up, initially around the Xerces and Xalan XML libraries. Maybe - maybe - Microsoft is starting to get on board with this kind of model now.

Re: The Weakness of the .NET OSS Ecosystem

#44
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…

I hate this attitude that negativity is unproductive. Pointing out a problem, articulating its impacts, and hypothesizing about its causes are essential steps to effective problem solving.

And I further abhor the notion that anger is not useful. Anger gets attention, and passion elicits empathy and thoughtfulness. Anger is motivating. Anger is a rejection of despair, which is the real enemy of change.

Re: The Weakness of the .NET OSS Ecosystem

#45

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.

Well, now that Microsoft's open sourced ASP.NET and working on .NET Core, you can add ".NET" to that list.

Re: The Weakness of the .NET OSS Ecosystem

#46
post #25
post #12

My perception is that F# is attracting the open source folks in the .Net community http://tomasp.net/blog/2015/why-fsharp-in-2015/

Ironically, I love F# but still waiting for F# on JVM before beginning any serious work.

Do you really believe that it'll ever be on the JVM? Why would Microsoft put any effort into that? CLR is now cross platform. If you want functional programming that is similar in style to F# (and ML-family of languages), check out Scala.

Re: The Weakness of the .NET OSS Ecosystem

#48
Re: the Akka.Net stuff, there is indeed an implementation of an Actor model framework - Orleans. Now it was developed in house at Microsoft and hasn't gotten a lot of attention from developers other than Microsoft employees, but it's there.

https://github.com/dotnet/orleans

Re: The Weakness of the .NET OSS Ecosystem

#49
This is right and wrong.

Right because yes there could be a ton more open source solutions out there. Also right because most of them are either shit, commercial or abandonware. This is a big problem. We imported a lot of stuff and found it was mostly crap (Nservicebus, justsaying come to mind)

Also wrong because a massive portion of what we do is a solved problem on .net. There's not a whole load of stuff to reinvent.

What I'd like to point out though is name me one platform I can build stuff for desktop, mobile, web, embedded, plugged into office applications, deployed by a single click from the web, deployed to single machines, deployed to thousands of workstations, will talk to just about anything under the sun from REST, SOAP, WS-*, databases, spreadsheets, document models, message queues, serial ports, pipes, TCP channels, has a request broker and distributed object model and has several data access methods from ORM, SQL, table gateway abstraction and has very decent tooling, provisioning, integrated deployment, testing, profiling and backwards compatibility going back 20 years all out of the box with no glue required?

On top of that there's support which is actually very good for everything above.

Nope there's only one and Java doesn't come close.

Re: The Weakness of the .NET OSS Ecosystem

#50
post #42

I'm glad that Microsoft is absorbing enough young guys who went through college realizing open-source is cool to actually influence their future direction, but based on the entire self-interested history of Microsoft ( https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish or http://www.pcworld.com/article/2901262/microsoft-tightens-wi... or http://techrights.org/2010/09/17/microsoft-management-mocks-... ) and…

Lots of downvotes, but I can relate to what you are saying. 10 years of working in a pro Microsoft organization trying to do PHP and Ruby development showed me that developers and managers alike bought into Microsoft's ideas at the time. Microsoft was good, Microsoft offered support, and open-source was just for hobbyists. 10 years of working with servers that were hostile towards openness, and 10 years of watching M…

I knew I'd get downvotes, but we are real people in a real community and feelings DO matter and have consequences which cannot simply be brushed aside, and those are my honest feelings on it, and I lived through it and saw it all (been a web dev, first frontend now backend, since '97). The last straw was when Microsoft was SO guilty that the judge couldn't help but be biased, which of course caused the antitrust case to get thrown out: http://www.politechbot.com/p-02198.html (note: I'm kind of against antitrust, but I am in favor of SOME punishment when a corporation is provably just being a dick, period).

I also love Ruby (I'm now trying to get into Elixir) so the IronRuby stuff resonates, I salute you.

> and 10 years of watching Microsoft blatantly steal from open-source and not give back

Oh you mean LDAP? ;) And whatever harm Outlook did to MIME or SMTP or... and not even going to mention IE

Post reply on HN