| Compared to what? To visual studio? It's bad. To rider? It's bad. To the level of support in vscode, for example, for typescript? It's bad. To using a potato? It's pretty good! To using a plain-text editor? Pretty sweet! To using the old omnisharp plugin? haha... is there anything that isn't better than that? Seriously though, if you want an honest answer: It's not that bad... but, its frustrating after using a different editor. They're now investing in making it better (1), and it is better than it was a year ago. Expect to see more improvements in this space. ..but like, yeah. Right now, it kind of still sucks if you're working in C# full time, compared to the serious alternatives. You can see common themes on the issue tracker (2), if you want a less anecdotal response, or perhaps dig through a couple of the juicy threads (3), that give you sense of the state of play right now. tldr; watch this space; if you're already heavily invested vscode, give it a whirl... but, if you're using a mostly-c# code base, you probably won't want to have it as your primary editor right now. [1] - https://devblogs.microsoft.com/visualstudio/announcing-cshar... [2] - https://github.com/microsoft/vscode-dotnettools/issues [3] - https://github.com/microsoft/vscode-dotnettools/issues/329 |