Visual Studio for Mac Retirement Announcement - Visual Studio Blog

https://devblogs.microsoft.com/visualstudio/visual-studio-for-mac-retirement-announcement/

29 points · 10 comments · view on lemmy.world

10 Comments

Spyros@programming.dev · 10 pts · 2y (4 replies)

MonoDevelop died for this.

(Disclaimer: I haven't used MonoDevelop to know its quality, I'm just tempted by the idea of a free cross-platform .NET IDE. Microsoft took MonoDevelop, forked it into VS for Mac, left the former stagnate, and now is killing its closed-source descendant.)

MasterBuilder@lemmy.one · 3 pts · 2y (3 replies)

Vs code fits the bill as a good cross platform .NET IDE. It is also a really good Standalone text editor.

douglasg14b@programming.dev · 6 pts · 2y (1 reply)

VS Code honestly kind of sucks for it, there's just so many small things missing or lacking.

Check out Rider, I was honestly surprised and switched over to it after 8 years of visual studio.

winky88@startrek.website · 0 pts · 2y

Rider is awesome - totally understated even if JetBrains does have a big fan base. If you'll notice, most non-MS video bloggers use it, and for good reason.

Spyros@programming.dev · 5 pts · 2y

It's a great text editor, yes. An IDE though, it is not. It gets close with various addons, but it's still not the same experience.

insomniac@sh.itjust.works · 3 pts · 2y

Rider is less bloated and stupid

tonytins@pawb.social · 3 pts · 2y

This explains why the latest preview didn't have 8.0 support.

Mon0@lemmy.world · 2 pts · 2y (2 replies)
[ removed ]
LeFantome@programming.dev · 1 pts · 2y (1 reply)

Code is missing a lot that Studio fans think they need. Rider is excellent though. So between Code and Rider, .NET devs are well serve on Mac.

I suspect that the success of Rider on the Mac is one of the reasons this got killed.

Mon0@lemmy.world · 1 pts · 2y
[ removed ]
rodolfo@lemmy.world · 1 pts · 2y

done a couple things with rider - on windows. well, the chance that the better c# ide is written in Java is not so remote

computertoucher5000@programming.dev · -1 pts · 2y

I'm not staking out the position that one is objectively better than the other by saying any of this:

I recently adopted neovim and I think it's going to be very hard to make me leave it. On the one hand, I love some of the vscode extensions I've got going, on the other hand, neovim + lazygit somehow just invokes the flow_state() much quicker-at least purely from the standpoint of being in an editor.

What's up with that?