I’ve tried vim on and off during college but never really had the time to fully get working with it. As it turns out the stress of two degrees is not conducive to “fun activities”. Now that I have a real job ™️, I’ve decided to finally try and use it this week full stop and I genuinely feel like a programming chad. There’s still a lot I’ll need to learn and probably overtime I’ll discover some inefficiency in how I’m using it now but it really does just feel good. I understand the hype now.

  • FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    23 hours ago

    There’s definitely an element of snobbery, and also of being lazy about tooling. Do you think once you become a talented dev you lose all human vices?

    Some of the smartest people in the world believe in an imaginary dad who lives in the sky and grants imperceptible wishes. Everyone is human.

    • sping@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 hours ago

      Lazy about tooling? The biggest point people make is that IDEs tend to work out of the box while the likes of vim or emacs need configuration and have an initially steep learning curve.

      Well, as in this discussion, some people sometimes also tend to raise a lot of features as if only IDEs have them, but that’s frequently just ignorance.

      • FizzyOrange@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        7 hours ago

        IDEs tend to work out of the box while the likes of vim or emacs need configuration and have an initially steep learning curve.

        Not in my experience. It’s very easy to design systems that break IDE support. People love adding all sorts of ad hoc build scripts that mean you can’t just press F5 or whatever. It takes discipline and caring about IDEs to not do that.

        And while people might love tweaking Emacs and Vim, it isn’t required.