![]() VSCode is clearly a threat as any large firm market dumping is to any company. ![]() If you want one application that can do everything under the sun, get VS Code. If you want to get work done and your use case fits into a JB product, use it. JetBrains has a way better UX and is more solid (hello enterprises!) and will eventually catch up to some of the more Revolutionary new VS Code features, but it has a lot slower update cycle. But my general feeling is that VS Code is more flexible and has more features at the cost of a worse UX, largely due to its open source nature. Since VS Code depends on open source implementations by plug-in maintainers/language servers for these, they tend to vary a lot from language to language. finally: refactor methods are wayyyy ahead in JetBrains products. setting up languages and projects in Vs Code can be exhausting and seemingly impossible sometimes (Monorepo…) Stuck in a seemingly infinite Index Rebuild multiple times. VS Code language servers seem to be quicker in building index. No finicky manual switching between test output and Debut Console needed like in VS Code. Tests and TDD work better out of the box in JB. ![]() JB Debugger is more convenient and easier to use Just an example: there has been a Ticket open in VS Code to enable moving the outline view to the right side of the UI for years and they say it is not possible because that would need some large refactor. UI customizability is miles ahead in JetBrains. Remote dev support is a lit better than JetBrains (also it is not in the free editions of JetBrains) this is especially frustrating if you use setups which are considered “exotic” by the devs (like having IPv6 disabled). stuff breaks and will not work for multiple weeks. My observations from daily driving VS Code insiders for half a year: However, I think it is not quite there yet, largely due to bugs which need to be ironed out. VS Code has come a long way and Is overtaking JetBrains by innovation speed it seems, largely thanks to its rich plugin ecosystem.
0 Comments
Leave a Reply. |