19 ms·
Can we trust Microsoft with open source?
- loldk 5y agoabsolutely not.
- hatmatrix 5y agoIs there any way to ensure commitment to open source from any commercial company?
- loldk 5y agoNo, but you can practically guarantee it.
- deleted 5y ago[deleted]
- capableweb 5y agoMicrosoft promising `dotnet watch` for a while and then dropping that certainly doesn't help with the already pretty damaged view of Microsoft not caring about open source developers. Here is the gist of the situation from Microsoft's point of view: > Throughout the last year we’ve been working to enable the best possible Hot Reload experience in Visual Studio 2022 and .NET 6. Part of our goal was to also explore making this feature available to customers through a variety of mechanisms such as bringing the full power of Hot Reload to as many .NET and C++ developers as possible when running through Visual Studio 2022 debugger, supporting Hot Reload when running .NET 6 apps without the debugger, and the very basic Hot Reload support we added to the .NET SDK tools through dotnet watch. > As we reflect on what was accomplished, and what is still in front of us, the backlog continues to grow. This includes many high value scenarios that will benefit the broadest number of developers, including focus areas such as .NET MAUI, Blazor, adding support more types of edits, more optimized experience when working with XAML apps, and much more. > With these considerations, we’ve decided that starting with the upcoming .NET 6 GA release, we will enable Hot Reload functionality only through Visual Studio 2022 so we can focus on providing the best experiences to the most users. We’ll also continue to pursue adding Hot Reload to Visual Studio for Mac in a future release. So, first they wanted "bringing the full power of Hot Reload to as many .NET and C++ developers as possible" but now they shifted to "focus on providing the best experiences to the most users". Best part of this whole thing is the pull request which was opened (https://github.com/dotnet/sdk/pull/22217 https://github.com/dotnet/sdk/pull/22217) but " locked and limited conversation to collaborators" straight after opening it as Microsoft anticipated the backlash but still went ahead with the change. Seems they still have a lot to learn before they can indeed be trusted.
- twodave 5y agoI didn't read that as, "Our focus is changing from A to B," so much as, "We originally hoped to ship A + B, but A ended up being more work than we expected. B is achievable and impacts more developers, so we're focusing on that first".
- 5e92cb50239222b 5y agoUgh. I've been using dotnet core on Linux since it was introduced. While it mostly works fine, I always had the feeling that Linux (and mac probably also) is a second class citizen. They care about Linux compatibility inasmuch as it allows you to build the application on a Linux-powered CI server and deploy to another Linux server. Developing outside of Windows? most of their tools are not available or have a greatly diminished feature set (for example, you can take a memory dump of a running dotnet application, but can't really inspect it without a Windows VM). If not for JetBrains Rider, dotnet development on Linux would be close to impossible IMHO. When looking for my next gig I'll probably be switching to something else.
- copperx 5y agoIs Jetbrains Rider acceptable for .NET work under Linux, or do you miss Visual Studio proper?
- 5e92cb50239222b 5y agoI actually preferred Rider even before fully moving my .NET work to Linux. If you have any experience with IDEA, you'll feel right at home (they are very similar and can be operated with pretty much the exact same shortcuts).
- xrd 5y agoVSCode is the editor I use for everything now. But this is big. Centralizing control with Microsoft in the drivers seat now seems really risky.
- capableweb 5y agoExcept if you do C#, which has limited support in VSCode compared to most other languages. Slightly ironic as C# is Microsofts own language.
- breakfastduck 5y agoI imagine that's generally a case of most C# devs just using full fat VS so the people who'd add the support to VSCode don't actually use it
- capableweb 5y agoGenerally yeah, but as mentioned in https://news.ycombinator.com/item?id=28969338 https://news.ycombinator.com/item?id=28969338 Microsoft also actively refrain from adding features to the dotnet sdk in order to have less people to use them, VSCode included, in order to stuff the same features into VS.
- formerly_proven 5y agoI'm honestly a bit surprised that people are still using Visual Studio (sans Code) these days. It was a decent IDE ten years ago, but nowadays I'd put it far down the list (not least because it means that you have to develop primarily on Windows which is... uhm... yeah, no thanks). Is the VS experience much better when you are using C# instead of C++?
- 5e92cb50239222b 5y agoPretty much all dotnet developers that I know (of) use VS. I am one of the few holdouts (Rider is miles ahead IMHO and is actually cross-platform).
- tdsamardzhiev 5y agoNo, but we have to. Hopefully they'd sooner or later be bullied into doing the right thing.
- skohan 5y agoMS is normally the ones doing the bullying
- tdsamardzhiev 5y agoYeah, that's a problem. To the person who downvoted me: I'd like to hear some arguments. Perhaps you don't need to. But that's irrelevant -- the world at large does. That's the main point of the post, too.
- theonemind 5y agoThe Visual Studio Code thing is kind of a shame. It seems like a variant of "embrace, extend, extinguish" inasmuch as things like Atom exist (which microsoft also owns, womp womp, but didn't for 3 years after Atom started). It competes in the space, keeps competitors weak by being the best so that it gets all of the users and mind-share and resources, but doesn't go all of the way with them because it could compete with their proprietary products...so while being the best is a good thing, it's not a good thing when it creates a monopoly-like product in a space good enough to suck up landscape resources so that no viable competitors not under Microsoft's thumb could ever start approaching parity with their proprietary products. Definitely dents Microsoft's nascent open-source credit with me and, like so much of Microsoft's history, seems actively damaging in a monumental way to the history of computing itself for Microsoft's benefit.
- simooooo 5y ago“keeps competitors weak by being the best” What
- deleted 5y ago[deleted]
- ognarb 5y agoVisual Studio Code has also some official extensions that are not open source and the official build contains a few proprietary features by default. The only thing I like with Visual Studio Code is that they were able to promote a cross text editor way to have auto-completion and other IDE-like features, thanks to the Language Server Protocol. Now I can use these features in Vim and Kate.
- jcelerier 5y ago> Visual Studio Code has also some official extensions that are not open source and the official build contains a few proprietary features by default. I don't understand how that is remotely ok. VSCode's main binary links statically against Blink (as it uses Electron) which is under LGPL, at the very minimum they should provide a way to relink that binary as per LGPL requirements.
- captainmuon 5y ago> The big issue here is that Microsoft has an internal struggle going on at the moment. On one hand they want to be seen as a new version of Microsoft who loves Open Source, but on the other hand they want to actively block advances in OSS projects like the .NET SDK which could undermine their own commercial offerings. For years, the narrative has been that MS doesn't want to give away their tools for free because they don't want to undermine the commerical offerings of their ecosystem. There used to be a ton of companies making development tools, components, and so on. Microsoft mostly made money with Windows, Office, and so on, so they could give away their own tools almost for free (but preferred not to in order to keep the vibrant ecosystem running). It is really odd that anybody at MS cares about whether VS or VS code or an external tool is more popular. Also this whole infighting between departments seems to be contaproductive. If I were top level management, I would tell people to get their shit together. If instead of working together to make the best products possible, a manager tells off an employee for working on the C# extenstion for VS (because it hurts his personal goals) I would at the very least reprimand the manager. That VS code has poor .NET support, or for another example that MS graphical toolkits have so much churn and they don't use them themselves, are really embarrasing mistakes. I'm sure people have been fired for lesser problems...
- pjmlp 5y agoIt has always like that, that is why we lost Managed DirectX, XNA, .NET Native, C++/CX, the Longhorn failure, MAUI vs Forms vs WPF vs WinUI vs UWP vs Blazor. I am not affected by this as licensed VS user, but I also don't like how this story has been playing, and join my voice to those complaining how this was handled.
- muzdave 5y agoIn 2000, I worked at a web company that was a “Platinum Partner” with MS, and we did a lot of consulting work with them for various large clients. Me and another guy were invited to come out to learn about this new platform that MS was building called “Cool”, which was the internal name for c# at the time, and the early forms of .NET. While we were there, Scott Guthrie (I’m 99% sure it was him) was supposed to lead us in some discussion but wasn’t there, and someone filled in for him. We learned later it was because he had been called into Bill G’s office and got dressed down a bit because Scott had basically created his own version of Apache web server to use within the dot net tools. It was rudimentary and temporary, but the reason he did it was because he had been trying for months to get the IIS team to give him a version of their server for use within the dot net dev tools, and they just kept putting him off. So he went around them and built his own. They found out, went up the chain, and Scott got dragged into the office to be told to cut it out and work with them instead. Granted, this is 20 years ago, so my memory might not be as crisp, but it stuck with me as a lesson that Microsoft was not a single company, but like 10-15 different little companies, and they competed among themselves as much as they worked together. And as OSS was coming up at the time I thought, “they have no chance to survive what’s coming.” I’m still not sure if I was wrong or not yet.
- politelemon 5y ago> I know what you think. You might think I’m reading too much in-between the lines here, but trust me on this one that I am not wrong. No, I don't think I will trust you as telling me to trust you is not a valid qualifier. And, I do think you're reading too much in between the lines. For example > but more importantly they also won’t deny it. Please stop with low effort clickbait. There are no mentions of all the positive outcomes that have emerged from their open source shift. In other words, it does focus too much on recent drama rather than putting this in the context of all their contributions. Nor, considering the title of the article, has there been any consideration for the overall ecosphere of the tech giants that are playing in this space. If you ask the question, then look at who the others are. I cannot think of two worse companies to 'trust' than Oracle and Apple and represent the antithesis of openness. There are existing contributors, Google and Facebook, who do plenty and can somewhat be trusted considering their nature, and despite their reputation. There you will find a similar pattern, some things are open and some are proprietary Looking at the context of their contribution over the past few years I would put them firmly in the latter category. The answer to the headline is: yes, somewhat.
- shikoba 5y agoNo.
- voakbasda 5y agoNo. I will never trust them. Fool me once…
- mbushey 5y agoYou learn fast. My version would be fool me 10 times. I wouldn't trust Microsoft with a bag of rotted potatoes.
- matheusmoreira 5y agoNo. When a headline asks questions, the answer is always no.
- indymike 5y agoLots of "commercial open source" products use limited features in the open source tool to sell the "pro version". Maybe what we're seeing is not MS being awful, but executing a pretty normal open/premium type strategy (hi there ElasticCo). As a developer I'd love to be able to use .NET like I do Python, Go, JavaScript and Nim (ok, and Java, too). I love being able to write software that can run anywhere, using the editors and tooling that I like. VS Code is amazing in that it fits into my world. VS on the other hand, forces me to run a specific OS, and use a prescribed tool chain. FWIW, sometimes the prescribed way might be better, but it's not the way I want to do it.
- thrower123 5y agoYou could use Rider. It performs much better than Visual Studio anyway. Visual Studio has fallen quite far behind at this point.
- n8cpdx 5y agoThere are a few scenarios where it breaks. UWP and Xamarin is dicey. Ironically, it hasn’t been able to edit android layouts involving ConstraintLayout and a few other common layouts/views for a few releases now (ironic because they also make Android studio, which has best in class android layout editing). Visual Studio is great for the common platforms/languages, but as soon as you try going cross platform or adding unloved platforms (UWP, Xamarin) it gets bad. Unfortunately, those also happen to be the things Rider is bad at.
- smitty1e 5y ago> Maybe what we're seeing is not MS being awful, but executing a pretty normal open/premium type strategy There is a difference of degree, if not kind. It's one thing for a smaller vendor to offer an 80% solution for free, and 20% enterprise features where there is competition to protect the market and the users. It's quite another for a monopoly-level player that, for example, owns GitHub, to flex and threaten the market. I'd support some serious anti-trust looks at what's going on across all of BigTech. MisterSofty is not alone in needing a review.
- RNCTX 5y agono.
- AlexandrB 5y agoIndividual people can be trusted, but trusting a corporation is a contradiction in terms. The leadership of any team can be replaced pretty quickly and goals can pivot on a dime. Or, like with Sun, the company may be acquired by another with completely different objectives. If you want commitments from a company, get it in writing (in this case in the license). I also don't get this part: > They won’t develop cool features like these any more and most frighteningly, they won’t accept pull requests or community contributions which could add these features back into the SDK - and that is a bleak outlook for the open source community in .NET. What stops someone from forking the SDK and adding this functionality? Or are there non-open-source components this all relies on?
- GordonS 5y ago> What stops someone from forking the SDK and adding this functionality? Or are there non-open-source components this all relies on? I've felt the benefits of Microsoft's OSS push over the last decade, and I've been an advocate for their work. As such, I've never felt the need to run VSCodium, and I've been OK with sending Microsoft telemetry from my VSCode install (though I would prefer it was opt-in, rather than opt-out). But now they are trying to have their cake and eat it too - they want to keep up the "developers, developers, developers" mantra, because they can deeply their tooling with Azure and nudge devs in it's direction. But they also still want to maximise revenue from their commercial IDE, Visual Studio. And as a result, they are half-arsing both goals, a strategy that is absolutely doomed. And you know what, for a feature like `dotnet watch`, it's just so completely unnecessary, as VS would still be a very different and vastly more capable IDE than VSCode. This really feels like some high-head in the background is pulling new strings, and I really don't like it. I'm also 100% certain that if `dotnet watch` is discontinued, someone will reverse engineer it (very easy with dotnet!) and release it as a third party dotnet global tool, which makes this whole situation even more pointless. I hope VSCodium does start to add in functionality that Microsoft is trying to keep for themselves, starting with the dotnet watch code that was written and not merged - extra functionality would be a very compelling reason to use VSCodium.
- deleted 5y ago[deleted]
- armchairhacker 5y agoI honestly don't really like VSCode or see the hype. To me it feels very clunky. I'm spoiled with IntelliJ but I also use regular Visual Studio Notepad++ and Vim and I've Xcode in the old days, and all seemed better than VSCode. #1 issue is that the extensions are all written in TypeScript and run in the background. When I click to go to a definition, rename, run, or even save, I get that "progress bar" and it takes at least a second. A lot of extensions are also buggy. Vs a "real" IDE like IntelliJ or Xcode, which does those operations almost instantly with significantly less bugs. If VSCode isn't a "real" IDE, then it competes with other text-editors like Notepad++, Vim (not counting advanced versions like Spacemacs), etc. But those are way faster and less cluttered because text editing is all they try to do.
- rudian 5y ago> I honestly don't really like VSCode or see the hype. To me it feels very clunky. It's funny because I've been trying WebStorm and it brings my i9 16" MacBook to a crawl so VSCode feels much "faster". It doesn't help that simple operations like renaming anything are multi-step processes or are just apparently missing (no apparent way to delete a file or visit its parent folder from the command palette) I agree with the rest. VSCode to me is just a little step up from Sublime Text for UI and base features, but it's still a far cry from proper IDEs like WebStorm (of which I like the proper refactoring features)
- xxpor 5y agoVSCode's remote editing extension is the killer feature. The only thing that comes close is TRAMP in emacs, but unfortunately since emacs is single threaded, any network blips means the UI is blocked.
- JoyrexJ9 5y agoVSCode extension are written in Typescript but most of them rely on a language server for things like refactoring, type hints, code completion etc. These language servers run as native process (written in Go, C# etc), so are (roughly) as fast as your machine is. If these operations take over a second it may be an issue with your machine or install of VS Code
- skohan 5y agoI'm generally weary of MS having too much influence over open source with Github and VSCode, particularly due to their history. My creep alarm went off a bit when I recently started a project to test the waters with TypeScript. I was asking on a forum how to deal with native JS dependencies without types, and he answer I got was "Are you using VSCode? It will just find the community maintained type packages for you". It seems to me that VSCode's "just click the button to solve my problem" style of UX makes it very easy for developers to become reliant on proprietary workflows without even realizing it. If one were to pursue an EEE strategy, this would not be a bad way to start.
- selectodude 5y ago> It seems to me that VSCode's "just click the button to solve my problem" style of UX makes it very easy for developers to become reliant on proprietary workflows without even realizing it. Certainly “making a better product that’s easier to use” isn’t something we should be discouraging.
- skohan 5y agoI think there's a difference between giving you powerful, easy to use tools to solve your problems with, and solving your problems for you.
- rg111 5y agoThey are not forcing you to use their solution. You can go your always go your own way. I am primarily a vim user with VS Code as my secondary editor. I have never ever used their one-click solutions. I have seen someone choosing "Yes" to everything VS Code said after installation, and in no time their machine was filled with bloat that they would never ever need. But I see this as a good thing. It is making programming set up easier for the uninitiated, which is good.
- throwawayboise 5y agoI disagree that making setup easier for the uninitiated is good. The uninitiated should begin with a bare-bones text editor and a shell prompt. If you don't understand what is happening from that level, you will never understand what is going on in complicated frameworks. You will be the programming equivalent of your grandmother who thinks Facebook is the internet.
- Kenji 5y agoNo.
- zmix 5y agoMicrosoft: Too big to fail. Open Source: Too good to fail. That's why Microsoft can't "own" open source. So they decided to "own" the open source developer by owning the source repository he uses, owning the editor, owning one of the most popular languages (Typescript) he uses, the command line shell, he uses along with grabbing all the Linux commands and make them available on their own platform. This is not about proprietary code (owning the code), anymore, but about owning the platform and making people use it. I doubt, they have a clear plan, right now, instead they hope, that it will play out positively for them, in the future. A few years from now, I wouldn't be surprised, if you'd need a Microsoft account to log into Github.
- skohan 5y agoI agree that they probably don't have a clear plan here. I would speculate that they saw the writing on the wall that Linux and OSS had won, and they just started doing anything and everything to gain influence in that space. And there's no company I trust less not to abuse that influence once they see the opportunity to use it in an anti-competitive way without consequences.
- ethbr0 5y agoThe plan, as near as I can tell, is watching Google leverage Chrome and Android user base into votes for standards. Microsoft finally realized standards and interoperability was the future. They also realized that a requirement of being able to extract profit in that future was having power to influence standards. Consequently, open source tools (and more importantly, the dev/user share that comes with them) get Microsoft votes. Either explicitly or via mind share. And when it's a corporate priority or matter of survival, they use those votes to advance Microsoft's interest. We've seen this with Chrome / web standards for years now. Most of the time it's good for users, but sometimes it's just that important to corporate reveneue.
- skohan 5y agoI mean MS basically invented leveraging market share to drive web standards. IE was famous for flaunting W3C and implementing things their own way, much to the chagrin of web developers even to this day. It's the kind of behavior which got their hand slapped for anti-trust in the 90's. It's hard to say it's "copying google", it's more of a return to form now that the regulatory environment seems to have relaxed on anti-trust.
- jeppester 5y agoWe can't trust MS with anything, and the same can be said about every tech giant. Therefore it really is a problem that MS has managed to get hold of github and npm. In my opinion it would be beneficial if this kind of "important infrastructure" belonged to a non-profit organization.
- TheRealDunkirk 5y agoIt is the runaway nature of our late-stage capitalistic "utopia" that large companies just absorb anything that touches their edges, continually growing larger, and absorbing ever more. Skype, LinkedIn, GitHub, StackOverflow, and Slack were all nicely-running, profitable businesses, with agendas that made them attractive to end users. But their owners all had a price, and now they're all part of monstrous companies with agendas that do not necessarily line up with mine. On the one hand, this is perfectly understandable. On the other, I think the government needs to stop these sorts of mergers and acquisitions to create vertical (as well as horizontal) monopolies. We're living in an age of modern-day "robber barons," and we need the government to return to policies from those days, including STEEPLY progressive taxes, and vigilant anti-trust action. Unfortunately, the Citizens United ruling will make this an impossibility until it is "repealed" with new law.
- amelius 5y agoBut what if China allows these mergers for their own companies, while the US doesn't allow them for SV companies?
- asddubs 5y agoI don't see how that would lead to anything bad happening
- gopiandcode 5y agoThere are a lot of things that China does that other countries don't do, some of these things are bad, and personally I wouldn't want them to be implemented where I live (social credit score, censorship etc.). I don't see how engaging in a race to the bottom with China here is a particularly useful line of thought.
- goodpoint 5y agoAbsolutely not. Look at Microsoft for 20 years and you'll see all the red flags showing up. Owning github, vscode and linkedin is yet another EEE strategy.
- CyanLite4 5y agoToo much FUD and overreaction from people who dont even use Microsoft products here. MS simply said they are prioritizing one particular feature for launch in 2 week for their premium (paid) IDE. Another company has already implemented this feature in a competitive IDE (JetBrains Rider). Mac support coming soon. Community can work on that feature themselves or wait til after the launch in 2 weeks for VS Code support.
- travisgriggs 5y agoThat’s a whole lot of writing before you get to the “Can we trust Microsoft with open source?” question. As interesting as all the murky politics are, I didn’t need all of the long form prose to build to that question. In fact you could have just straight up led with the question. And then answered it even more simply. Any of Nope Probably Not Hell No Not Even would have worked. I’m not sure why this is such a drama or surprise to anyone.
- Ginden 5y agoThis is quite issue with any big product - open source never found widely applicable model of operating that isn't dependent on some companies. Linux relies heavily on corporations using it. Gecko is dead without Mozilla - if Mozilla bankrupts, no one has enough manpower to develop Gecko. Even if code is GPL-licensed and in ongoing development, main contributor can easily force their design choices on downstream forks. If you redesign some system, downstream forks have to reimplement their changes on top of refactored code. And they don't have enough manpower for that. Well, governance of open source is probably not solvable, like most of human relations.
- skohan 5y agoThe problem is when an open source project is owned and controlled by one large player. It's much healthier to have diverse stakeholders with different interests, none of which is completely in control, as is the case with Linux.
- CyanLite4 5y agoJetBrains did their own Hot Reload feature for Linux. The community is working as it should. The problem is everyone wants premium features for free. HotReload is a new feature, existing folks don’t have it now. If you want it on Linux, it’s going to cost $13 a month for a Rider license. Otherwise, keep developing without HotReload as devs have been for the past 5 years for free.
- Ginden 5y agoWhen I was talking about "unsolvable", I meant there is no single "best way to do it". All choices have tradeoffs. "One large player" can make hard, but neccesary choices. Multiple stakeholders can have conflicting interests, so they can stick with conservative way. One large player can use its control in ways detrimental to users. Multiple stakeholders can go with incremental changes that benefit everyone involved. There is no silver bullet.
- skohan 5y agoIdk I get what you are saying, but at least for me personally, if I am investing in making something part of my workflow, it makes me really uncomfortable knowing it's fate is in the hands of only one corporation who's interests can easily become un-aligned with my own. Slow progress can be frustrating, but it's better than being left out in the cold from one day to another.
- mjw1007 5y agoI'm concerned about the Language Server Protocol. I get the impression that its current state is something like CSS in the era of Internet Explorer 4 to 6: there's a published specification which Microsoft is nominally behind, but the de facto standard is "What Visual Studio Code does", and there's nontrivial divergence between the two. Can anyone who works with LSP indicate whether that impression is accurate?
- kinjba11 5y agoWhat does "nontrivial divergence" look like? LSP appears to be alive and well with editors that are not VS Code. The entire point of LSP is to decouple the text editor from the language, and it works. https://github.com/search?q=language+server+protocol https://github.com/search?q=language+server+protocol If VS Code has more support for LSP it is because Microsoft has poured money into it, invented LSP to begin with, and popularized it with VS Code to begin with.
- aaaaaaaaaaab 5y agoNo, of course not! https://en.m.wikipedia.org/wiki/The_Scorpion_and_the_Frog https://en.m.wikipedia.org/wiki/The_Scorpion_and_the_Frog
- mad_vill 5y agoI would be pretty skeptical of anything that is owned by the devdiv division (github, dotnet, etc). It seems like they are still looking for ways to replace the revenue they lost from the classic VS model. As for anything in the Azure org, I wouldn't be too worriedT They just want to wrap a managed service around an OSS project and call it "contributing to the community". It seems like there was some OSS innovation coming in from the deis acquisition, but years later all msft got from them was the helm dumpster fire, and I believe the founder just left to go to Digital Ocean. The Kinvolk acquisition is interesting also, but I have a feeling that it will pan out the same way.
- linuxhansl 5y agoThe better question is: Can we trust Microsoft with .Net Open Source? Open source that is somewhat close to a core of a what a company is doing is always a fine line to walk. See: ElasticSearch, MongoDB, MySQL, Databricks' Deltalake, Oracle's GraalVM, et al. This development is (generally) very unfortunately, and for those using .Net very annoying. But let's not forget, overall Open Source is great, and it's great that Microsoft has (finally) turned in that direction. There are a lot of other, successful Microsoft Open Source projects.
- cratermoon 5y agoCan we trust any organization dedicated to profit and shareholder return with open source?
- jpm48 5y agoThe chaos I'm getting with vcpkg at present seems to say not! I love the idea of vcpkg and it used to make life so much easier as I gave my students a list of packages to install for their homework and all was fine. Recently packages seem to get updated and break, there is no "easy" way to specify versions of packages. And in general it takes months to fix simple bugs. There seems to be over 1K issues at present. I know it's a difficult project but still could be done better.
- Henk0815 5y agoI understand that MS is still here to make money. Everybody wants to do that. What i don't understand is to risk the good will of the open source coummunity, by denying a core flagship feature another competitor (flutter/google) has included for free. I donk think this is a smart choice, even if i am in it for the money.
- ripley12 5y agoThe especially wild thing is that this decision mostly harms .NET in VS Code – another Microsoft product. Rider’s implemented hot reload on their own, so this isn’t helping against Visual Studio’s main commercial competition.
- VMtest 5y agoI made a note on similar happening somewhere... if somebody is interested 1. https://news.ycombinator.com/item?id=28779342 https://news.ycombinator.com/item?id=28779342 | I'm sorry 2. https://github.com/dotnet-foundation/Home/discussions/39 https://github.com/dotnet-foundation/Home/discussions/39 | I'm sorry 3. https://www.google.com/search?q=.NET+github+enterprise+hacker+news https://www.google.com/search?q=.NET+github+enterprise+hacke... 4. https://news.ycombinator.com/item?id=28847178 https://news.ycombinator.com/item?id=28847178 | Use of GitHub Enterprise 5. https://github.com/dotnet-foundation/Home/discussions/59 https://github.com/dotnet-foundation/Home/discussions/59 | Use of GitHub Enterprise 6. https://github.com/dotnet-foundation/Home/discussions/40 https://github.com/dotnet-foundation/Home/discussions/40 | Change in .NET Foundation Leadership 7. https://news.ycombinator.com/item?id=28794352 https://news.ycombinator.com/item?id=28794352 | How the .NET Foundation kerfuffle became a brouhaha 8. https://robmensching.com/blog/posts/2021/10/6/how-the-.net-foundation-kerfuffle-became-a-brouhaha/ https://robmensching.com/blog/posts/2021/10/6/how-the-.net-f...
- deleted 5y ago[deleted]
- fouc 5y agoI'd be interested in seeing a similar list of this except in the Google/Chromium space, but it's probably less obvious since they maintain Chromium themselves..
- tannhaeuser 5y agoGiven most indie F/OSS is on github where MS gets maybe a few pennies from clicks, I guess the case has been settled. Notable exceptions being software by ASF, LSF, and a couple other orgs.
- ThePhysicist 5y agoI think Microsofts' long-term plan is to get most developers to use cloud-based coding environments, which is not unlikely given that software stacks become more complex to the point where setting up a local development environment is really hard. Once they achieve that they're in a very good position to sell their own cloud services by making the integration into the development workflow really smooth. So their acquisition of Github and the large effort invested in VSCode as well as privileging their own software stack over competing solutions makes perfect sense, business wise. It probably won't be good for free software though.
- meibo 5y agoSetting up a local dev env is easier than ever on Windows. WSL, tooling, the new terminal, it's all there.
- frozenport 5y agoIt was always easy, just install vs code
- MathCodeLove 5y agoEven easier than that: git bash and docker.
- skohan 5y agoJust wait until you try linux
- kovac 5y agoI started off with Windows development. Later on I developed using Windows terminal and WSL. I've also done development on Mac. Then one fine day I tried Linux. It blew my mind. What is coming to Windows now is a pale imitation of what Linux has been having for decades. Amazing terminals, terminal multiplexers, tiling window managers, keyboard driven tools, package managers... I really regret those years lost.
- jaaron 5y ago
- xvilka 5y agoJust leave .NET for enterprise and move on to the newer languages and frameworks, like Rust, for example. In case of F# - OCaml.
- cryshana 5y agoCall me naive or uninformed, but I think everyone is overreacting. I have been using .NET for many years now, preferring VS Code or similar editors for work where I am totally in control of what is going on behind the scenes. I have been extremely satisfied with the direction Microsoft has been taking .NET and also GitHub/VS Code in recent years. The hot reload feature has been introduced in .NET 6 preview builds - emphasis on "preview" builds. I personally haven't used the feature a lot but have heard it worked great for a lot of developers. And now with .NET 6 GA date quickly approaching, Microsoft is wrapping up the .NET 6 release. This of course means moving any unfinished work to .NET 7, such as full AOT that I was personally looking very forward to. And even MAUI etc... So after reading their latest blog post on their decision to move the hot reload feature to only Visual Studio for .NET 6 GA, I quickly understood they probably just didn't have time to finish the feature / reach an acceptable level of quality for the dotnet CLI, so they just moved it for a later release - like any other unfinished feature. Of course this upset a lot of developers that were already using it successfully in their workflows, but let's be honest now, it was always a preview feature. You shouldn't take preview features for granted. I do agree, however, that Microsoft could've handled this better - they could've added like a "preview/experimental feature" warning when using hot reload via the CLI or something and kept the feature there as is - but I'm guessing they wanted to keep their CLI clean of unfinished features. It's not like they said they will never release it to everyone - just that it will be available through VS and VS for Mac for .NET6 GA. And if Microsoft truly did this for their own "evil" reasons, why was this feature available in the preview builds to begin with? It's barely been a few days since the blog post, and the backlash is already huge - people are already losing trust in Microsoft and they haven't even given a response yet.
- Henk0815 5y agoi think the differents is the lak of technical responses on the github issue from ms employees on why this was cut. This leaves only politcal reasons, which the normal ms staff don't make.
- cryshana 5y agoI agree. It is indeed a bit worrying. I am guessing everyone is quiet because Microsoft wants to give a single unified response. And needs some time to prepare and make a decision. I just hope this will get resolved soon without any issues and we can move on.
- blackoil 5y agoIf all true it is a very bad signal for .net I have been primarily a Java/Go developer. I like C# as a language and have been actively following development of .net for some time with intention to play a little deep with asp/blazor for some side project. If now Linux/Mac become 2nd class citizen I am no longer interested in the platform as no way I'll move servers to Windows and no near plan to change my dev machine to Windows. So better to drop .net as an option.
- 2OEH8eoCRo0 5y agoTrust is a weird word. Talk is cheap, what are they doing? I think Microsoft has been behaving pretty well lately and that's worth something. With that said, I still would never "trust" them. I don't understand people being spooked about Microsoft and open source. I've always viewed open source as a greased pig. Being open means anybody is free to fork and go elsewhere so the fact that they don't must mean a need is being met. I think the bigger threat these days is everybody being dazzled by top to bottom closed solutions like Apple's processors. I wonder if other companies will follow suit to keep up and start vertically integrating their chips too. Just my opinion.
- DeathArrow 5y agoIt's a kind of a weird move from Microsoft. Is Satya Nadella - the man that pushed Microsoft towards Open Source - still Microsoft's CEO or the position was take over by bad guys and girls like Julia Liuson? It's kid of a Dr Jekyll vs Mr Hyde. You can not have the cake and still eat it. I guess the push of .NET and other tools towards Open Source would yield motre bennefits in the long term than trying to castrate it in the hope they will sell a few more Visual Studio licenses. The company I work for is developing a big product using .NET. But it does it because it runs on Linux and it can nicely be integrated with many open source tools. If .NET wasn't open sourced, I guess they wouldn't have used .NET. I used Visual Studio until now because I genuinely prefer the experience, not because I was forced into it because some features were taken off from open source .NET tools. I do understand that people want to develop on other OS-es than Windows and using other IDEs than Visual Studio. And Microsoft has to understand it too if they want .NET to continue to be successful. NET only has two paths: to continue being open source and to flourish or to die. >NET running only on Windows and/or with only good tooling available on Windows will die. If they push .NET towards being closed - it's their right, they pay for the development - they might win a small amount of money on short term but they will lose everything in the long term. I hope they aren't idiots.
- pjmlp 5y agoBack in .NET Core 2.1 days, I did a porting project from .NET Framework into Java, because the customer in question wanted to go into UNIX (Red-Hat Linux more specifically), and .NET Core required a rewrite anyway, they decided to take the opportunity to move away from MS ecosystem, as they were fed up with rewrites. This kind of decisions kind of confirms those actions.
- Mikeb85 5y ago> It's a kind of a weird move from Microsoft. It is but it's been Microsoft's MO from the beginning. They seem incapable of not trying to lock people into their ecosystem.
- cryptica 5y agoI think they cannot be trusted in the long term. Even when they start out without ulterior motives, as the company evolves over the years, the ulterior motives start to creep in - Slowly and predictably, the tech becomes proprietary again. Vendor lock-in is in Microsoft's DNA. They know how to add lock-in slowly and quietly over many years. That's a big part of why I'm saying away from Microsoft-controlled language ecosystems like TypeScript. I can see Microsoft tightening its grip; how they achieve lock-in and shift towards proprietary is so subtle, most people don't see it coming until it's too late. I don't know if even the Microsoft employees who are implementing the changes see it coming; it seems to be subconscious; second nature to them.
- nathias 5y agoNo, they started copying Google's strategy, first become the infrastructure then exploit your position. Stop giving them the whole open source infrastructure for free.
- TheRealDunkirk 5y agoIf this stands, I don't want to ever see anyone on this site denigrating someone for bringing up EEE again.
- jodrellblank 5y agoSo now it didn't stand and they rolled it back, we can denigrate people for bringing up EEE? How about no denigration, you explain how Microsoft removing a feature from a Microsoft product preview was ever going to extinguish anything? Or how Microsoft putting some features for-money in Visual Studio is EEE but JetBrains charging for features in Rider isn't? That is, say you are a .NET/Linux dev today, you fork the .NET framework under its MIT license as of October 2021, and Microsoft never add another feature to .NET for free, {blank}, then you can never use your fork again because it has been extinguished. What happens in the {blank}, in your view?
- Nux 5y agoNo.
- rackjack 5y agoAh, the eternal cycle of: Microsoft does something bad, then people move to Linux, then they get dragged by Linux's rough new user experience, then they leave Linux, then things are fine for a while, then people mock Linux users for being paranoid, then Microsoft does something bad...
- AstroDogCatcher 5y ago[flagged]
- sedatk 5y agoAs a former Microsoft employee, and as someone who has been a fan of post-Satya Microsoft, this has been a very disappointing development. Microsoft needs to stop cashing trust for profits and that won't happen until they see the PR losses cost more than profit gains of such actions.
- advael 5y agoThe answer to that question has always and will always be no, and anyone who ever thought otherwise is a sucker, frankly. This is a company whose entire ethos and business model was built from the ground up to be about proprietary software for proprietary software’s sake. It is a company that has consistently tried to leverage any foothold it has in any space to wrap up tools and force people to pay for them. It is a company founded by Bill Gates of “open letter to hobbyists” fame, who said “Own the API”, who in the COVID crisis went and talked a vaccine producer out of opening their vaccine IP. No company can be fully trusted, but if you ever believe MSFT is working on FOSS without an agenda to harm it you’re a fool, and if you think contributors or even department heads within the company will or even can change this you don’t understand how working for a big company works
- drummer 5y agoThe short answer is yes. The long answer is no.
- znpy 5y agoIn my opinion one of the dumbest things that we're all doing is trusting companies that do not make their earnings from open source with open source. Microsoft only goes so far with supposedly loving open source. Kf they love open source so much, why don't they open source something really interesting instead of a toy editor like vscode? I'm thinking of something like sqlserver or their compiler tollchain or their userspace runtime library.
- mensetmanusman 5y agoAs with every aspect of trust in our lives: Trust, but verify.
- donatj 5y agoNo.
- BiteCode_dev 5y agoYou can't trust any big corporation with anything, period. Nor Microsoft, nor any other. It's not a matter of morality, it's a matter of scale. At their scale, the entity takes priority over individuals, and it will always do what's good for the corporation, and only the corporation, unless obligated to. In a capitalist society, this means it will always do what's profitable unless a stronger player, competition or the state, strongarm them into doing the right thing. So no, you can't trust Microsoft with open source. But right now, it happens Microsoft interest and the open source community are aligned. So keep your eyes open, don't put all your eggs in the same basket, assume it will change. Certainly don't let them control your stack. But do enjoy the ride. They have skills and resources, FOSS can benefit from it.
- CyanLite4 5y agoUpdate: MSFT has reverted the changes. https://github.com/dotnet/sdk/pull/22262 https://github.com/dotnet/sdk/pull/22262
- zmj 5y agoReverted: https://github.com/dotnet/sdk/pull/22262 https://github.com/dotnet/sdk/pull/22262
- Yuioup 5y agoAnd that is the promise of Open Source. That it will endure as long as there are individuals willing to carry it. Sad that Microsoft dropped "dotnet watch". Maybe it might come back in a different form. John Carmack managed to release an unlocked Oculus OS going against his Facebook paymasters. That was probably an ordeal. Maybe somebody within Microsoft can fight the good fight and bring Open Source .NET to the masses. Maybe not today, but someday...
- louthy 5y agoThey’ve reverted it (merged). It feels like the damage is done though https://github.com/dotnet/sdk/pull/22262 https://github.com/dotnet/sdk/pull/22262
- albertopv 5y agoTruly mismanaged it, trust is hard earned but easily lost. I guess there are reasons .net never really got into enterprises.
- moffkalast 5y agoDamn, they tagged half of all github users for review.
- NoImmatureAdHom 5y agoI would like to see a better model for funding FLOSS development. Maybe efficient cryptocurrency microtransactions or something like that. Every time I hit your repo I pay you $0.001, or every time I run your package I pay you the same. Voluntarily, of course. I want to do this now, and I do have recurring donations for some projects, but it could be frictionless and automatic.
- vermaden 5y agoDid you not learned it through all these years? Can you trust Microsoft on anything? Of course not - what were you thinking ...
- deleted 5y ago[deleted]
- holografix 5y agoI’m kinda surprised by the level of naïveté displayed by the community. Of _course_ there’s infighting. Do you think the VS team is gonna see their product value be eroded by free tools and take it lying down? Absolutely every company has infighting. The bigger you are the more infighting and disagreement. Infighting about product development prioritisation, marketing budget to promote new features etc etc. When companies are selling multiple products, some that overlap in their usefulness to customers you can bet there’ll be infighting. VS Code is a wonderful tool. You can’t expect that MS will make it 99% as good as a paid version.
- pxc 5y ago> Do you think the VS team is gonna see their product value be eroded by free tools and take it lying down? VSCode features can't make VS any less useful. They only make it less ‘valuable’ in an abstract, market sense. Why would the people actually making VS give a shit about that unless they're larping as their bosses? Or by ‘the team’ do you actually mean something like ‘whatever VP is in charge of the team’?
- anonporridge 5y ago[flagged]
- irensaltali 5y agoRevert PR is merged https://twitter.com/shanselman/status/1452020875973124098?s=21 https://twitter.com/shanselman/status/1452020875973124098?s=...
- samaman 5y agoAs someone who was an avid swift developer, I can see how people can get attracted to building OSS for .NET or Swift, and how it might even be necessary in many cases given the lack of feature update by the companies. But, after leaving the world, I just really hope more devs see that they aren't valued by these companies for building such open source, and in continuing to validate their products through continued fixes, we are only making them stronger. Maybe I have a very pessimistic view, but I've started looking very literally at how companies make money from any open source work they do before using it so I know what they want of me in the future and to see if I support their business model or not. Its for this reason I picked using Singularity over Docker because I just know that a federal lab + contractors for scientific work will actually stress test and continue paying for the software while docker, who ultimately doesn't then a profit yet, may either get bought by one of the FAANG+ or have to start aggressively curtailing access.
- simonblack 5y agoNope. And never could. Remember "Linux is a cancer"? and "Embrace, Extend, Extinguish"? MSFT has never changed its corporate genetics. It can't.
- james_burden 5y agoOpen source is just an ideal so the question is just can we trust M$ with software in general. I think the answer is obvious.
- fb03 5y agoOfftopic, but related: I am RELIEVED the `dotnet watch` removal was reverted [1] [1]: https://github.com/dotnet/sdk/pull/22262 https://github.com/dotnet/sdk/pull/22262