Programming

17668 readers

150 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Pulsar, the best code editor (optimizedbyotto.com)

submitted 10 months ago by otto@programming.dev to c/programming@programming.dev

60 comments fedilink hide all child comments

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 !pulsaredit@lemmy.ml

you are viewing a single comment's thread
view the rest of the comments

[–] BatmanAoD@programming.dev 24 points 10 months ago (2 children)

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@programming.dev 16 points 10 months ago* (last edited 10 months ago) (1 children)

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@programming.dev 3 points 10 months ago

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

[–] varsock@programming.dev 3 points 10 months ago (1 children)

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@programming.dev 4 points 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.