found this in an extension description today:

Why not use the Dev Containers from VS Code? Because Microsoft Devcontainer is a proprietary extension incompatible with VS Codium.

Why it is not on VS Code Marketplace? Because Microsoft is a VS Code gatekeeper and won’t allow anyone to publish an extension if it uses Proposed API. Except Microsoft and its “partners”, of course.

Meanwhile, these API are the only way to implement an extension like Open Remote SSH or Devcontainers.

Microsoft promises to allow everyone to use these API and publish extensions based on them in the future, once these API are “stable”. But it’s been many years since Microsoft first published an extension backed by a proposed API. It has also published many other extensions supported by the same API. However, the API is “unstable” and doesn’t seem to be going to stabilise anytime soon.

  • Mikina@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    14 hours ago

    I’ve been slowly starting to get used to Helix, doing a tutorial in either that or VIM (since it has similar keybinds, but a lot better interactive practice tools, like VimHero or VimAdventures) whenever I have time and feel like it, to get used to the motions and navigations. I still can’t imagine using it to actually code when I need something done, but I did notice gradual improvement in my efficiency. It’s more of a marathon, though.

    In the last few years, enshitification was the final motivation that pushed me towards better habits, like self-hosting, discovering Fedi, stop watching YT, de-google, switch to Linux as a daily driver, etc. I’m kinda looking forward to finally being forced out of IDEs into Helix.

    • morbidcactus
      link
      fedilink
      English
      arrow-up
      1
      ·
      13 hours ago

      I 50/50 helix at work, already my go to at home (though I still have codium for some stuff, don’t use it nearly as much.