Previously (with comment volume): "Visual Studio for Mac Retirement Announcement" (39 points, 2 months ago, 7 comments)[0], "Microsoft is discontinuing Visual Studio for Mac after major overhaul" (116 points, 111 comments)[1], JetBrains also did 65% discount when it was first announced [over now] (56 points, 64 comments)[2]<p>[0]: <a href="https://news.ycombinator.com/item?id=37325427">https://news.ycombinator.com/item?id=37325427</a>
[1]: <a href="https://news.ycombinator.com/item?id=37326419">https://news.ycombinator.com/item?id=37326419</a>
[2]: <a href="https://news.ycombinator.com/item?id=37369946">https://news.ycombinator.com/item?id=37369946</a>
Visual Studio for Mac had its roots in Xamarian Studio, which had its roots in MonoDevelop. Each one has always been a rebrand of the previous product.<p>(Edit: I forgot to point out that Visual Studio for Mac never appeared to be a port. It always appeared to be a "clone" of Visual Studio with a very similar UI.)<p>They've always been rather buggy and unstable compared to Visual Studio on Windows. They were a nice way to do C# on Mac without needing to load a VM; and for the last few years I really appreciated that C# was getting "first class" support on Mac.<p>I hope C# works well under VS Code.
Probably for the best - been a VS developer for many, many years, since the first version - but the Mac version was never even close to as good as the Windows version - as much as I wished it was, as my Mac is my primary machine.<p>They either needed to kill it, or make it at least as good as it was on Windows - guess they decided killing it was easier.
In all fairness, having being forced to work on mac recently for a cross platform application, the nuances of the macOs I hear dotNet people complain about are honestly NOTHING compared to how bad the Visual Studio for mac experience is.<p>We tried the Rider trial and it was a far superior experience, but the price wasn't justified for our use case.<p>I and others configured nvim to just work, and some others just stuck to vscode with the cli. Not one person wants to use the Visual Studio anymore. It's wild how Microsoft missed a great opportunity as I find the machines quite good, and the Windows experience with Visual studio is genuinely impressive.
An older version of the underlying source code remains available: <a href="https://github.com/mono/monodevelop">https://github.com/mono/monodevelop</a><p>That said, a comment in one of the open issues indicates that it is incompatible with .NET Core.
I assume they always kept it shitty as to not cannibalize VS Code, which does get a lot of use (obviously it's very popular). If you ever used it you'd see that it doesn't feel like normal Windows VS, and it doesn't really feel like a good native Mac app either.
One solution to keep on using VS on Mac, for those that are (a) weary of VS Code (b) not willing to change to a (paid) JB Rider, is to use something like Parallels to emulate VS on Windows.
I wonder how many cumulative calories were expended on the mini anxiety / disbelief attacks caused by n number of people momentarily misreading this as "Visual Studio Code" rather than "Visual Studio".<p>Not that I'm the biggest VSCode fanboy although I use it constantly. And not that I even own a Mac anymore come to think of it. But still, the wording of this post definitely contributed to global warming.