3 ms·

Same boat. Team is primarily M1 MBPs. Backend APIs are .NET 6 Web API in C#. Deploy to AWS Graviton2 instances. Build in GitHub Actions and AWS CodePipeline

Same boat. Team is primarily M1 MBPs. Backend APIs are .NET 6 Web API in C#. Deploy to AWS Graviton2 instances. Build in GitHub Actions and AWS CodePipeline (yuck!). Frontend is a mix of React (Next.js, externally facing) and Vue (internal tooling) > No friction points that I can think of... Well... I use both VS Code and Rider. I'd say that OmniSharp is a friction point because it's still just a bit janky in some edge cases. As long as a team is willing to pay for Rider (100% worth it), dev experience is great. If not, just be prepared to get used to the quirks of C# on VS Code with OmniSharp and get comfortable with the CLI (which you should anyways). The modern CLI is so good compared to old msbuild.

cutler 4y ago
Have you considered Visual Studio for Mac? That would be a more obvious choice than VS Code, surely?
- CharlieDigital 4y ago
  I do full stack development and Vue, React, JS/TS is so good in VS Code, that I can live with the quirks of OmniSharp. I love how fast an light it feels (compared to VS). I have not personally used VS Mac, but from what I've seen of it (other devs that used it), it looks like a downgrade. But devs using VS Mac all switched to Rider a few months back and never looked back.
  - cutler 4y ago
    Yes, Rider is my personal favourite. I go for the full IDE experience so VS Code falls short.
- donny2018 4y ago
  Visual Studio for Mac is evolving fast. Today it's much better than it was a few months ago. Now it is a good option for backend development.
  - cutler 4y ago
    I still have problems getting VsVim to install after recent VS Mac updates. Any IDE without a Vim plugin is a no-op for me.