Change of heart? Why? I think they are doing a pretty smart move to be friendly towards open source community, but it's not because I believe they changed their mind and want to contribute to the open source world, instead, I simply believes they embrace open source community is because it's good for business.
You see, open source software these years became pretty good and infrastructural. If Microsoft can't be a part of it, then they will soon be obsolete. And they don't want to be obsolete, so they just can't afford to not be a friend with open source.
The real thing that I curious about is what would happen when Microsoft managed to re-dominates the software market (in both user and enterprise end). Will they still be friendly with open source community after that?
It was always stupid to be against OSS from a business perspective and so long as developers hand over their IP on a platter it always will be - Microsoft would be really stupid to turn away free money, and they seem to realize this now.
Often, it was "programmer solve thyself".
Businesses have only been employing significant numbers to work on open source projects for the last decade.
GitHub is just a signal to people who have been out of the loop, bloomberg and many linux developers.
When I start dropping my apps on their systems, they might be surprised how well they run.
With DotNet Core we have an extremely well crafted language available on all Windows and Linux. It's a great move on part of Microsoft.
Before ASP.NET MVC, there was Castle Monorail. Before Entity framework or linq2sql, there was Nhibernate.
It was amazing times. It was clear Scott Guthrie started moving microsoft in that direction back in the day, after ALT.NET movement started proving success and showing an alternative to people.
DotNet Core debugger is proprietary . You can only debug apps within Microsoft environment according to their license.
Same thing for most of the azure tools , you are only allowed to use them within Visual Studio.
I don't really called that "all in open source" .
It's gimmick to give C# devs the illusion of a choice.
Try to build , run & deploy a C# app on AWS with Atom. You're gonna have a bad time.
And regarding your claim, you can do all of that, even with Vim if you want. You just have to build some scaffolding.
After all, they can't be expected to implementing everything for everyone. More than that, they were actually nice and created LSP (https://langserver.org/) and now they're thinking about a Debug Adapter Protocol (https://github.com/Microsoft/vscode-debugadapter-node/issues...) that would do the same thing for debugging.
It's not "Open Core" if the core is not open. In this case a debugger is core part of a language. It's a very clear movement in order to keep C# devs within their ecosystem and guarantee revenue with Azure. They loose money here , they must get it somewhere else.
This guarantee a total monopoly over the .NET ecosystem , Rider is probably one of the only tools that tried to offer an alternative they are stuck with the exact issue of not being able to bring the debugger because of that hostile license policy.
>Even the GitLab everyone's talking about in this context is Open Core.
I never talked about Gitlab and I don't care about them.
Don't be mistaken about MS , almost every move they do as a double intention behind it.
Just to name a few :
One MS engineer is core member to Webpack & Angular , why ? Windows Server dashboard is written in Angular , it's a critical product, they need some controller there.
One MS engineer is core contributor to Electron, why ? VS Code is powered by electron , it's a critical product, they need some control here as well.
One MS engineer is core contributor to Vue.js , why ? Azure is investing hundred of millions in China and Asia due to insane growth over the past 5 years, they need a good image in asia.
If you think MS has changed , you are delusional about the situation.
People keep bringing this up as if it's some evil plan, not a legacy problem.
The debugger is based on Visual Studio's closed source debugger. Visual Studio is a major paid product. It's not simple to just extract an integral feature from a paid product.
Why? This isn't a technical challenge. As far as I know, the actual debugging engines are pretty isolated modules with some alternative interfaces already available (e.g. cdb). So where do you see the real challenge?
That might be because I'm deeper into web development though, and both TypeScript, and VS Code are great contributions.
Maybe I'd feel different if I worked in ML, and used Tensorflow daily.
FWIW, I don't and wouldn't use a source code repository of Google's or Facebook's, either. In fact, rather than open a GitLab account, I started self-hosting a year ago. GitLab made that easy. I also looked at Pagure.
they’ve gone insane.
https://opensource.microsoft.com
and all of these are active and well managed with microsoft employees engaged in communication.
Dart, Go,
Android,
Chromium,
Protocol Buffers, Java Guice/Collections, C++ Abseil
Plus a bunch of minor things
https://opensource.google.com/projects/list/featured
and stuff Google contributes to but doesn't lead.
So there is much less of a network effect which makes it less valuable. One example: most open source modern OO languages, e.g. Kotlin, Scala, target the JVM, and so are interoperable. Whereas C# is in a closed Microsoft bubble of open source. If it had an LLVM or Java backend, it'd be much more useful.
and saying “most open source modern OO languages ... target the JVM” is not accurate. if you mean modern OO JVM languages, then yea, of course, but that is satisfied analogously by the .NET languages.
the c# and f# compilers, .NET core (libraries and framework), and core CLR (the runtime) are all open source and cross-platform. there isn’t anything closed about it. i don’t know what you mean by “closed microsoft bubble of open source”.
why do the .NET languages need LLVM or JVM implementations to be useful? again, that doesn’t make sense.
Google however maintains a few products that can easily be considered standard, or at least will find their way in any other developer stack.
if you use google’s open source projects are you now a google developer?
and visual studio code is probably used more for web development than it is .net work. it certainly is the major selling point of it on the website.
I really don't know a lot of people who do anything with the MS stack. And those who do code on and for Microsoft (which already is a minority)
I personally don't know anyone who switched from Atom or Sublime to VS. Only VS users I know have been using real VS before.
My SO migrated everything off Github back on Sunday when rumors broke, deleting the account & repos that had commits and contribs going back years.
Consistently, one of the first questions I ask friends and acquaintences who go to work across the lake to work for MS in Bellevue or Redmond is whether they are on an Embrace or Extend team. Most are on Embrace/Rewrite our own version but "better" teams.
Microsoft has changed, but they're no Red Hat or Suse.
Additionally, I find it comical that you would even suggest that a company that has sued other companies for using open source software is even in the conversation with companies that have championed open source software since their inception.
There is no undo button. All you can do is be better than what you were. If Microsoft really wants to start doing a better job in the open source community they can start by agreeing to never sue another company for using Linux.
They want an undo button? It's right under their nose: stop with the bullshit auto-update that re-enables itself, document all telemetry and make a big button to disable it.
But they don't do that, do they? Any idea why? Spoiler: it's all fake bs again, take one flashy but insignificant step forward and take 3 covert snake-like steps back.
I'm not a fan of the telemetry either, but they do have it all documented now, which is more than, for example, most phone manufacturers: https://docs.microsoft.com/en-us/windows/privacy/basic-level....
And I'm not sure what Windows is supposed to force users into things they don't want. I haven't had an issue with turning off functionality and having it be switched back on during updates - I guess it must happen based on the complaints, but it's not something I've experienced.
Microsoft aren't the only company that need constant security updates: I've never seen any complaints about Chrome's.
But really that's my only complaint!
When updates that only add telemetry (Windows 7), or that upgrade an installed Windows 7 / 8 to Windows 10 without even asking, among other garbage, are classified as "critical security updates" by Microsoft, it really should come as no surprise that people disable all automatic updates in response.
They didn't exactly help themselves, firing their QA team, and using their users as the test platform.
OVH, who owns the largest datacenter in North America uses OpenStack, they're actually one of the largest contributors. Red Hat & IBM both seem to be really pushing private deployments as of late for their larger clients that already own large DCs.
They are the worst quality cloud provider, IMO.
Even if they plan to keep good will support for strategic relational reasons, that good will is easy to go away with strategy changes.
We've seen this over the years with previous code hosting platforms. If the platforms betrays it's users, developers are not scared to mass migrate to something else. The onus is now on Microsoft to keep developers happy or risk losing their $7.5B investment.