[ed_blackburn]

I am experimenting with dev containers at the moment. I am finding them very useful for setting up environments and they work as advertised. Where I am struggling is the poor support in the Jetbrain's suite and having to accommodate different editors. We need more tooling and editor plurality for dev containers to take off.

[ricoxicano]

Have you considered the possibility that Jetbrain's users are left behind while devcontainers have already taken off?

[sunaookami]

Has it taken off though? It reeks like a semi open-source Microsoft product where the only goal is to lock you into VS Code.

[ed_blackburn]

Yes, I’m aware of the politics, but I’m not about to force developers to switch editors for a single feature. We’re seeing real competition again, with new entrants like Zed, and that’s a good thing—engineers should be free to use the tools they’re most productive in, whether that’s VS Code, JetBrains, Neovim, EMACS, Helix, or Zed.

Tooling that claims to improve developer productivity should be editor-agnostic. If Microsoft can’t fully support that, an alternative standard will emerge—because, ultimately, locking developers in rarely works long-term.

Besides, the VS Code golden age has passed. It’s well on its way down the enshittification ramp.

[Alifatisk]

Have you tried Gitpod or Devpod for Jetbrains?

[ed_blackburn]

We are really happy with GitHub, that's our source control and CI platform: I think editors are fungible but not source control,ALM,CI etc. I hear your point though and I see how the loop is being closed with cloud providers hosting your code and editor so they can simplify deployment to their cloud. It's partially why I was surprised to see JetBrain's Fleet fall away, I thought it was their play at separating the editor FE and BE...