[sdfhbdf]

Hmm i don’t think you can compare IntelliJ which is a fully featured IDE with refractor functionalities, full text search, debugger and so on to a vim setup with plugins in docker container, just because they both edit text. This what the author did at the end of the write up. It’s like comparing jQuery to NodeJS, yeah they both generally are for JavaScript but serve a different purpose.

[adriancr]

vim, gdb, grep, cscope, ...

Just because you are not familiar with his setup doesn't mean it's not at feature parity and more.

Hell, he might even be running intellij in docker if he wishes.

Saying this as I have a similar setup with emacs.

[sdfhbdf]

For me what you just listed are a couple of tools that fit a specific workflow - seems like C or C++ development.

IDE is an Integrated Development Environment. So I think strapping a few tools together with no real influence over one another doesn't seem to constitute an IDE.

Unless you wanna argue that putting these tools into a Docker image makes that container an IDE, then I don't know, maybe? Whatever floats your boat in the end.

Using a JetBrains product you pretty much just pay for the support and "works out of the box" features. You can roll your own LSP, AST Analyzers, shell scripts that bundle it all together and call it an IDE, but I would still be on the side saying it's just a bunch of tools and they're not "integrated"

[adriancr]

I am suggesting - vim + plugins or emacs + libraries that use those tools. All integrated as you say.

Your IDE also uses gdb or similar for debugging, common compilers like llvm for compilation / code indexing, common analyzers.

You will have references, definitions, code search, debug, completion, etc all within the editor (in my case emacs)

It all works great and much faster then out-of-the-box IDEs, works within terminal too... no x11 needed.

That still requires some fiddling initially to get it working but once you have your setup its a matter of just pushing it to docker.

Now... the drawback is the time spent to get it, but what i'm saying is don't be dismissive, try and imagine what's possible with old tools.

New tools are also nice in that they avoid that setup work, you can push these too in the docker container and use them the same way.

[kamac]

I agree, the title of the article is a bit misleading. In general, you’d still need an IDE installed on the host machine, which can then connect to a runtime on the container. With VS Code and remote containers, it’s quite easy.

Alternatively, maybe it’d be possible to have the container expose an IDE over http (possibly vscode through the browser?).

[stult]

VNC/RDP via Guacamole or some other VDI solution can provide this with relatively little effort. But it sort of defeats the point. Using your local IDE to connect to a container allows for a snappier, more responsive development experience than a VDI can provide. Plus remote containers is basically just ssh. So a lot less bandwidth and general overhead than a full on VDI solution, and you don't need to have a full VNC server set up on your containers.

[egwor]

The same concept still works; they could have installed IntelliJ and copied over all of the plugins and settings?