Today we are announcing the retirement of the Visual Studio for Mac IDE. Visual Studio for Mac 17.6 will continue to be supported for another 12 months, until August 31st, 2024, with servicing updates for security issues and updated platforms from Apple.
  • Spyros@programming.devOPM
    10·
    1 year ago

    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
      8·
      1 year ago

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

      • Spyros@programming.devOPM
        6·
        1 year ago

        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.

      • douglasg14b@programming.dev
        6·
        1 year ago

        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.websiteEnglish
          1·
          1 year ago

          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.

    • LeFantome@programming.dev
      1·
      1 year ago

      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.

  • computertoucher5000@programming.dev
    1·
    1 year ago

    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?