The Era of Visual Studio Code

Re:The Era of Visual Studio Code by gerash on Tuesday September 22, 2020 @10:40PM (#24562403)

I have had the same experience. VS Code looks like a fine lightweight text editor plus a marketplace of plugins with variable degree of maturity and interoperability whereas IntelliJ is a mature and polished IDE.

All IntelliJ lacks is two things: 1. Being a lightweight editor with syntax highlighting which IIUC they are / have already built 2. Remote development where the IDE is just the front end running on, say, a laptop and the computation runs on a remote work station

[ Parent | on HN ]

Re:The Era of Visual Studio Code by modernerd on Wednesday September 23, 2020 @02:19AM (#24563589)

I prefer IntelliJ to VS Code but for me IntelliJ also lacks the ability to:

Disable plugins on a per-project basis. (I currently put up with plugin exception reports for other language plugins in projects for unrelated languages.)

Enable or update plugins without a full restart. (This is getting better but many plugins still need a full restart.)

Sync all plugin settings (for example, AceJump plugin settings aren’t synced).

Split the terminal pane horizontally.

Open a file in a vertical split from the navigator or search everything box. (I want to believe I missed an easy way to do this; someone let me know if so!)

Set alpha keyboard shortcuts in quicklists.

Style the title bar colour on macOS to match the editor background.

Write a quick script to add missing IDE functionality without boilerplate or build tooling.

Add a command line run configuration. (There are workarounds but the original feature request remains open after 7 years: https://youtrack.jetbrains.com/issue/IDEA-112256 )

I can do all of these in vim and Emacs and most in VS Code.

They’re nitpicks and no editor or IDE is perfect. I think I feel the pain points with IntelliJ more acutely because for many of these I can’t fix them myself.

[ Parent | on HN ]