TL;DR OSS has conquered the world, forcing even the biggest players of commercial software market to adjust their strategy to this fact. But the original idea of OSS has got somehow twisted in the meantime: everyone uses it, without feeling obliged to contribute. What is more, consumers expect flawless quality, but rewards for providing this quality are very ephemeral (so very few take
New .NET is around a corner. Tomorrow (2016.06.27) we'll put our hands on freshly baked .NET Core 1.0 & ASP.NET Core 1.0. What can (should) we expect of this new version? How will tomorrow (& days after) differ from what we already know?
Microsoft is honestly open about all the technical changes (well, what can you expect - it's
Btw. so did/do I, so don't treat it as another "smart-ass sage tutoring the world how awesome he is" kind of post ;P
People love OSS due to various reasons, naming just few:
- some love it, because there are no license fees (which doesn't mean it's FREE - this is a terrible mistake, but not the one I'll be focusing in this article
The more I think about it, the more I am against strict code ownership ("my stuff = my commits"). I mean - yes, there has to be someone who 'owns' the piece of functionality (for the sole purpose of supervision, roadmapping, etc.), but the more people put hands on it, the better. And the reasoning I have is not code-focused (related to quality, tech debt,
As you can see in the title. End of story. Period.
Maybe it’s just bad luck, but within few last weeks I had quite a few similar experiences - I was looking for a component to be integrated (as on-premise) in larger solution and usually there were plenty of solutions available, but none of the options were available on Windows (or .NET