The key to being productive as a programmer is to have a great code editor. I have been an avid user of Atom since 2014, and its successor Pulsar since now in 2023.

Pulsar (former Atom) is still the best code editor in my opinion. It is easiest and fastest to use, has all the nice productivity boosting plugins and is overall great for all the same reasons the Atom was great. 🚀

See also [email protected]

  • BatmanAoD
    282·
    11 months ago

    I know several world class programmers, and interestingly, the commonality among them is that they all seem to use Vim as their code editor. Many people I know who think of themselves as world class programmers use Emacs.

    What a burn!

    • TechNom (nobody)English
      214·
      11 months ago

      More like a personal bias in the form of a distasteful snark that the author thinks is funny. Their demonstrated knowledge about Emacs in the article indicates the worth of such remarks.

      • BatmanAoD
        4·
        11 months ago

        Yeah, I commented elsewhere on the misinformation regarding emacs in the article.

      • IvarK@lemmygrad.ml
        31·
        11 months ago

        You wouldn’t happen to think of yourself as a world-class programmer by any chance?

        • TechNom (nobody)English
          4·
          11 months ago

          If I were, I wouldn’t be hanging out here, would I? BTW, I use both Vim and Emacs.

    • varsock
      5·
      11 months ago

      As a former Vim user myself, I have to say I really dislike screensharing with coworkers who use Vim. They are walking me through code and shit pops up left and right and I don’t know where it comes from or what it is I’m looking at. Code reviews are painful when they walk me through a large-ish PR.

      These days, I tend to bring my vim navigation/key bindings to my IDE instead of IDE funcs to Vim. Hard to beat JetBrains IDEs, especially when you pay them to maintain the IDE functionality.

      • zygo_histo_morpheus
        4·
        10 months ago

        Pair coding with vim is a skill in itself (for the vim user). You can make things a bit easier to follow by making liberal use of visual mode for example. I have a CoworkerMode command that turns on smooth scrolling via vim-smoothie and cursorline, and I’ve also added some stuff to the neovim right-click menu so that I can explicitly right click go to definition for example. It can be worth switching editor sometimes, but it’s not always worth it if you’re in the middle of something.