VSCODE VS GOLAND 64 BIT
VSCODE VS GOLAND UPDATE
VSCODE VS GOLAND 32 BIT
VSCODE VS GOLAND MANUAL

I actually worry a bit that they're losing this and becoming more 'California' with efforts like Fleet and Space because those look suspiciously like large rewrites rather than incremental refactorings. It's been continuously upgraded and refactored for 20 years now. They have historically also dogfooded their own philosophy. And Java's general features and robustness compared to HTML5/JS mean they can ship features and improvements at an incredible pace. The JVM largely abstracted JetBrains from both transitions (albeit in recent times they've had to become co-maintainers of Swing), allowing them to focus on just adding features.

VSCODE VS GOLAND 64 BIT

It took forever to go to 64 bit and never made it to non-Windows platforms.

VSCODE VS GOLAND 32 BIT

Classical Visual Studio got knocked out of the race a long time ago, partly because it was written in C++ and failed to make the jump beyond 32 bit Windows. The tools they're using are fundamentally well designed and it shows. Also, Java/JVM has been a good platform for them over the years. There are some, most notably Kotlin, but by and large cool but expensive-to-develop new features are things you pay for, e.g. JetBrains seems to try to limit the number of free-for-browny-points projects it runs. The thing is that without profits to justify continued investment, executives at firms like Microsoft or IBM eventually get bored of old projects and quietly defund them. They matured in an environment where the go-to IDE was Eclipse, also free, also funded by a behemoth. But JetBrains have seen off free competitors many times before. 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.

VSCODE VS GOLAND UPDATE

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.

VSCODE VS GOLAND MANUAL

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.

Vscode vs goland