Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
myss442425dDon't know, maybe they just want to support projects which were done from honest belief for free open source software versus the ones that just joined the hype train and are there just to try and wash away their money hungry corporate image.
Imo there are a lot of better alternatives then dotnet core out there and the fact itself why its free now has probably something to do with Microsoft realizing they've milked most of money from that one so now they're just trying to pretend to be the good guys and care about foss.
Idc what anyone says, until they publish their whole Windows source code, no matter how crappy it is in background, I'll never consider a Microsoft as a genuine open source contributor.
Dotnet core was primarily a community project. It arose from the long efforts of the former alt.net community evangelizing open source in the .net community.
Many major contributors to dotnet are also significiantly accomplished in the Linux, open source space. Miguel de Icaza built mono (he is also responsible for Gnome) and xamarin, absent any influence from Microsoft because he understood the value of what they were doing. Anders Hejlsberg made typescript, also open source. Erik Meijer introduced async await to dotnet, and then went on to add it to a half dozen other languages. Meijer also made reactive extensions, which has since been ported open source to 30 languages and spawned the reactive programming movement you see everywhere nowadays (rx, flux, flow).
Your suspicion of the bonafides of the people contributing to the coincidentally MS-adjacent open source initiative are misplaced.
I like C# and all but I'm not 100 % convinced when it comes to its eco system
.net core was a great step in the right direction, even if microsoft tends to talk down the impact the open, community-driven development had.
What's a bit fishy around it is the different tools, like the debugger for vscode being only applicable to be used with visual studio products etc.
also all the different ".net"s are a huge chaos and I can only pray that .net 5 will change this once and for all
I finally crawled my ass out of a cave and learned Node and React and Vue, and as you guys know like hundreds of npm packages that goes along with this style of frontend...
It looks cool. I used .net a lot back through asp.net and then just .net from 2008 - 2012. Lot of DNN sites. Few for some really really big vendors. Loved it frankly, even liked Visual Studio,... but the work dried up.
But, I honestly don't think my mind can take doing that, and the other IoT stuff I've been doing... and then going welp, lets go code in F# in a completely different OS for the evening.