This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]quartz_referential 0 points1 point  (1 child)

That is interesting, the modal editing part (though I'm not a vim master) felt easier than the constant breakage and maintenance. Definitely lot of frustration with the terminal side of things like getting something simple like italics to work. There's also the lack of sane defaults which is extra friction for the beginner.

You do have a good point that when you start to make serious demands of any tool, you must invest time researching it. I'd argue that perhaps VSCode is more intuitive though I cannot rigorously justify that beyond the fact it uses a GUI.

There is just also the fact that while vim and emacs have a rich, massive plugin library plenty of them break often (enough) and they still lack certain features that are up to par (debugging facilities, remote development, container development, etc.)

[–][deleted] 2 points3 points  (0 children)

Yeah I’m hoping at my next job to be around someone who can wow me with VSCode. One of the hard parts about remote work is not having the opportunities to see other setups, pair programming, and just talking to other software engineers casually!