Live data from Hacker News

Reflections on IDEA vs VS Code

archive.vn

121–130 of 413 posts

Re: Reflections on IDEA vs VS Code

#121
post #77

HN deserve better content than this, while the topic is interesting there are too much errors, unadjusted logical quantifiers and omissions to make this biased writing worth a read.

HN deserve better comments than this.

Sure asking for better epistemological quality should be disincentivized.. Do you realize the distopy you imply?

Re: Reflections on IDEA vs VS Code

#122

In my opinion, one killer feature of VSCode is the ability to connect to WSL, remote server and Docker container. As someone mainly developing on WSL2, I use this feature everyday. I only use Idea when I need to use Java or Kotlin, because its language support is really good.

I agree with this; I bought the professional license of PyCharm on the basis of its "remote development" functionality which I assumed would meet the (admitted) easy "it just works" standards of everything else in Idea.

It never worked, not even close and I ended up dumping it and returning to VS Code because the remote stuff (particularly to linux VMs and containers) was a deal-breaker.

Real missed opportunity I thought, it had been a long-standing bug when I looked into it, and very very oversold as functionality present in the professional version.

Re: Reflections on IDEA vs VS Code

#123
post #97
post #90

Earlier quoted context omitted.

How does the open source IDEA plus php plugin experience compare to phpstorm?

The plugins for alternative languages (PHP, Python) are available only for IntelliJ Ultimate / paid. It's not available in free / open source IntelliJ So either [1] you buy IntelliJ Ultimate & get Java + other languages (PHP, Python, Ruby, etc except .NET and C++) or [2] you buy the language specific IDE (cheaper) like PhpStorm, PyCharm, etc

That didn’t used to be the case. You used to be able to add the Python plugin to the free IDEA ide and that would give you java + pycharm - but only the free tier features of pycharm.

However, if you used the paid IDEA, adding the Python plugin gave you full PyCharm capabilities EXCEPT that IDEA was always based on version N of the core IDE platform where PyCharm was based on N+1 version, i.e. the smaller pycharm IDE sometimes had some newer platform features than the IDEA ide which led to occasional differences between IDEA + Python plugin vs PyCharm.

I switched to VSCode last year and let my licence lapse for Intellij so things may have changed.

What i will say, despite having moved to VSCode and being entirely happy - Intellij is the better platform. It’s the difference between 80% and 99% though, and the VSCode 80% is good enough. If i went back to full time dev, i would buy another jetbrains licence.

Re: Reflections on IDEA vs VS Code

#124
post #30

I used to think VS Code was going to be a threat to JetBrains IDEs considering how fast its iterative development was (thanks in large part to the productivity of JS + Web renderer) but its never seems to quite be able to reach the feature-set, polish & intelligence of JetBrains IDEs. Every IDE function appears to be better implemented in JetBrains, whether it's Code Analysis, Refactoring, Navigation, Running/Debuggi…

Agree, PHPStorm for me is a productivity monster

Re: Reflections on IDEA vs VS Code

#125
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 is interesting to me and makes me question what I missed on setting up JetBrains products. I moved away from them because of their lack of support for standard tooling like eslint and pep8. It felt like JetBrains editors wanted me to set up lint rules by their spec and I had to set it up in their editor configs. I’ve always been able to add the VSC plugin for a language and everything just works. With JetBrains…

> I moved away from them because of their lack of support for standard tooling like eslint and pep8.

Sounds like something went wrong. These both get auto configured for me. I even get correct completion suggestions to disable the rules inline or at the file level for both eslint and pep8. The only thing I’ve had difficulty with is Prettier but that was improved recently. Email is in the bio if you need any help :)

Re: Reflections on IDEA vs VS Code

#126
post #10
post #3

I don’t really see IntelliJ and VSCode as competitors. VSCode competes with atom and other full-featured text editors (vim, emacs) ... its got great adoption amongst the newer generation of programmers that think those editors are old school and user hostile. VSCodes Java, Python, and Golang support is miles behind IntelliJ. FWIW, on my team at Microsoft where we write a lot of Go, theres a 50/50 split between Intell…

Interesting. I have used IntelliJ for Java for as long as I can remember and can't imagine using anything else. For JS and Go I use VSCode. I wonder if it's just what I started with and am used to. I've tried to use Intellij a couple of times for Go, but end up back on VSCode.

I'm the same way. Java/Kotlin in IDEA, front-end (js/ts/css) in VSCode, and Go can be either but usually VSCode. I don't really want/need more than what VSCode provides for it.

For Ruby, I'm lost without RubyMine--I work on a huge codebase and lean on the superfast search (with default "*.rb, !*test*" files) a lot, usually restricted to a project subfolder.

I'm really glad they renamed Gogland to GoLand--gland is weird (unless maybe I'm doing Monads in Haskell or something).

Re: Reflections on IDEA vs VS Code

#127
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…

Outside of the JVM space, I share the complete opposite sentiment. Go and Rust support in the past few months (close to a year at this stage) have been vastly better with LSP than with intellij (or the more specific products). Rust-analyzer literally just works for me with the vscode rust-analyzer plugin (intellij wouldn't work after a few minutes of googling etc, not a great experience) and I've consistently seen Goland be outperformed in OOTB experience by gopls, as a highly active member in Go online communities catering to helping many new developers.

Re: Reflections on IDEA vs VS Code

#128

In my opinion, one killer feature of VSCode is the ability to connect to WSL, remote server and Docker container. As someone mainly developing on WSL2, I use this feature everyday. I only use Idea when I need to use Java or Kotlin, because its language support is really good.

I've seen this being mentioned in other comments, and besides WSL2, I've used PyCharm (a close relative to IDEA) connected to containers, Vagrant and plain VMs for years. I suppose the rest of the IntelliJ products have the same support, and WSL2 being rolled out, obviously?

Re: Reflections on IDEA vs VS Code

#129
post #32

Earlier quoted context omitted.

Goland is great if you have IntelliJ muscle memory, I haven't tried using IntelliJ directly for Go though, Imagine it's probably sub-optimal. You do have to pay for Goland also.

I love Goland, and it's honestly one of the products that I very much like to pay for. You can eventually pay a one time fee and use it forever (without updates). I'm also using it for Rust, but it's missing CLion's powerful debugger UI - but I think that gdb is good enough :-)

That’s how every JetBrains IDE subscription works, though. If you pay for a year, you get the version at the start of that year for perpetuity.

Re: Reflections on IDEA vs VS Code

#130
VSCode won't kill IDEA, but it is a huge warning for Jetbrains

They better invest A LOT MORE into solving slow startup and performance issues that are plaguing their IDEs since the beginning

Time to ditch Java on the desktop, or invest in a native AOT compiler / or use GraalVM

Post reply on HN