I have not used an IDE since I ditched Turbo Pascal in middle school, but now I am at a place where everyone and their mother uses VS Code and so I’m giving it a shot.

The thing is, I’m finding the “just works” mantra is not true at all. Nothing is working out of the box. And then for each separate extension I have to figure out how to fix it. Or I just give up and circumvent it by using the terminal.

What’s even the point then?

IDK maybe its a matter of getting used to something new, but I was doing fine with just vim and tmux.

  • @NeryKEnglish
    18•2 months ago

    I do. I used to juggle between Code::Blocks, PyDev, NetBeans and others, depending on projects. I find VS Code kind of fulfills the promise of Eclipse of being an all-purpose IDE, without the bloat Eclipse became synonymous with. It really clicked for me when I started using devcontainers. I am now a big fan of the whole development containers concept and use it in VS Code daily…

    Write and lint Markdown documentation ? VS Code Build fairly complex C++ software ? VS Code Debug slapped together Bash scripts ? Also VS Code Hobby-grade Python fun times ? Believe it or not, also VS Code

    • @[email protected]
      1•2 months ago

      Code::Blocks

      This still exists? I played around with it’s portable app eons ago.

      development containers

      How does that compare to Vagrant?

      • @NeryKEnglish
        3•2 months ago

        Code::Blocks is still chugging along, albeit at a glacial pace.

        The rise of Docker has made containers very popular in the last 10 years or so. Nowadays you can run a single WSL2 VM on Windows with a Linux distro, and run any number of containers inside it. Vagrant is useful if you need full-fledged VMs for your environments.