Live data from Hacker News

Reflections on IDEA vs VS Code

archive.vn

301–310 of 413 posts

Re: Reflections on IDEA vs VS Code

#301
post #252

Earlier quoted context omitted.

Not sure how many devs code in a single language these days. I go back/forth between Go, Dart, and C++ every day, so using one IDE like VSCode (with the familiar features from extensions to shortcuts to snippets) is a big help.

I wish JetBrains looked exactly into that, and deliver one IDE with above (^^^).

I don’t since you end up with either complex configuration to surface language specific tasks. Having well thought out defaults, tools, etc by separating them out into different IDEs allows for ease of use you couldn’t get with one IDE to rule them all approach. Yes, they sell different IDEs that share a large core but I think the incentives are well aligned for sustainable business focused on developer satisfaction.

Re: Reflections on IDEA vs VS Code

#302
post #60

I use IntelliJ daily. I think when LSP gets there VSCode can catch up and fill the IDE gap, but until then it doesn't come close to IntelliJ in terms of functionality (though sometimes the perf of IJ makes me want to switch but it has been feeling a lot better on the M1). LSP needs to make 2 major improvements in order to to get wider adoption: - Improve package/runtime support detection (Go modules, npm, virtualenvs…

This comment doesn't make much sense. LSP is just a protocol, implementing package detection is the responsibility of the language server.

The second thing you're asking about sounds more like a unified LSP client which is totally possible. It would actually be pretty easy. VSCode could actually improve this a lot since language clients are mostly boilerplate.

All that said I think you're undervaluing what LSP/DAP actually gets you. It's a language agnostic API for PL tools, which includes compilers and virtual machines. All you need to be able to do is parse JSON and you can begin writing a reactive compiler that integrates into any code editor.

Re: Reflections on IDEA vs VS Code

#303
post #16

> The key technology here is probably the Language Server Protocol I've been working on an LSP implementation lately, and I have to say so far the reality falls short of the promise. I feel like what LSP should be is a clear, simple interface for implementing IDE-like features for any language, but my experience is that it is incredibly arcane and difficult to use. The main issue is the documentation. It has a high-l…

Marketing-level docs and then fine-grained API docs sounds very MS.

I would be happy with fine-grained API docs but there's no JSON-RPC spec I could find

Re: Reflections on IDEA vs VS Code

#305

Earlier quoted context omitted.

I wonder if you have had the chance to use a Jetbrains IDE with a professional license. Doing so gives you access to more or less the content of all the other "flavors" as plugins (it's basically all IntelliJ underneath). For example, I've been using PyCharm for both our python backend _and_ our React + Typescript frontend, all in the same project window, with the same features regarding syntax, linting, refactoring,…

There is most certainly a lot baked into the language-specific editors that isn’t in IDEA proper. That said, the fact that they all share IDEA’s gubbins makes it massively easier to jump between languages and frameworks for small jobs than I ever thought would be possible. Having a set of tailored environments that also share keybindings and most common features makes for a fantastic (and really under-appreciated) va…

That is incorrect. It is the same code running underneath.

There are differences in default config, and sometimes the independent versions have a faster release tempo, but it's the same language code.

Re: Reflections on IDEA vs VS Code

#306
post #187

Earlier quoted context omitted.

Not sure how many devs code in a single language these days. I go back/forth between Go, Dart, and C++ every day, so using one IDE like VSCode (with the familiar features from extensions to shortcuts to snippets) is a big help.

It’s worth noting you can set up shared settings between every Jetbrains IDE which will sync up all of your keybindings, color schemes, etc.

I've never got it to work reliably between different types of IDEs (Android Studio and Intellij for example)

Re: Reflections on IDEA vs VS Code

#307

Earlier quoted context omitted.

in my experience Intellij looks better if you have coded in Inttellij first (especially Java) and then moved to othet tools. Intellij offers a lot of custom behaviours that IMO programmers start coding the "Intellij way" (let's call it Intellij muscle memory for lack of a better definition) on the other hand going from vi to Emacs to Sublime to VSCode is less of a problem and people tend to honestly judge strength an…

Something Java accidentally did was be impossible to code without an IDE, in part because of its type system. People wrote really good IDEs for it, aided by the type system. At some point, they realized they could use what they learned and adapt the IDE to other languages.

It wasn’t accidental. JavaBeans were explicitly designed for “wiring up” UIs in IDEs and are the reason the horrible getters/setters are ubiquitous in Java.

It’s also why NetBeans was a part of Java for so long (is it still?)

The main reason I started using IDEs was automatic imports. Funnily enough, when I went from VSCode to GoLand, one of the things I miss is the import management, which is better in VSCode. But for everything else, especially refactoring, GoLand is better.

Re: Reflections on IDEA vs VS Code

#308
The great advantage of a Jetbrains IDE is the solid integration of all the components for a particular language. Bolting together extensions in VS Code has never gotten me close to the efficiency of a dedicated IDE from Jetbrains. I use both for their strengths and always have an instance of both running.

Re: Reflections on IDEA vs VS Code

#309

I almost use always vscode via it's ssh remote development feature. In my experience this thing is flawless and indistinguishable from local development. It's hardly believable how good they've made it. The idea vs. code is something i don't buy. Each has its use cases. Idea has great tools for android development, it's just tightly geared towards that, which is especially good for someone that is not a main android…

Just curious but what is the use case for needing to have your source code on a remote server while you’re editing it?

Re: Reflections on IDEA vs VS Code

#310

> Meanwhile, JetBrains seems to be staying afloat mostly thanks to hard work and sheer luck. I don't think they keep ahead simply by hard work and sheer luck. Once you look under the hood at Intellij it's clear that they have significant architectural advantages. While VS Code is a text editor that uses LSPs to provide refactoring and navigation, Intellij is a refactoring engine with a good text editor on the front.…

Thanks for this comment. This analysis of the internals is much more informative than vague divination that the post author pulls from their gut.
Post reply on HN