4 ms·
This just reads like anyone who's flirted with both editors. "I'm really familiar with <editor A>, and I see the merits of <editor B> and wanted to use it, but
by colordrops 10y ago
This just reads like anyone who's flirted with both editors. "I'm really familiar with <editor A>, and I see the merits of <editor B> and wanted to use it, but in the end I'm very familiar with <editor A> and decided to stick with it". Not much insight here.
- sdegutis 10y agoAlso, "I learned $A and got really good at it, and shunned $B figuring $A was superior in every way, but my experience with things similar to $B convinced me to learn it, and ultimately I realized I like it much better than $A, and have been happily using $B for years now."
- brudgers 10y agoThere are significant architectural differences between Vim and Emacs which mean that each better accommodates some workflows better than others. In the author's case the architectural differences manifested in the mechanisms for extending core functionality. Vim was initially designed to do one thing well...edit text. Emacs was designed to do whatever the user wants whether that's editing text or something else or choosing their own definition of what it means to edit text (e.g. org-mode). Each approach has value for different tasks for different people at different times. That doesn't mean that one is not better than the other for a particular person/task.
- majkinetor 10y agoIt doesnt matter what were they initially designed in some abstract sence. Nobody would question that those 2 are primarilly editors and that it is their most important function - editing and navigating text (and along, text interfaces). That means that vim must be better as its workflow is more efficient for that (thanks to the 2 modes and speed that object motion combinations give) and more healthy (without producing RSI which means I can physically do vim more time then emacs, a point mostly ignored by people ). Both can do basically anything nowdays so the argument of particular workflow suiting better different people does not hold. Its just that some people dont want to invest time into learning vim because vim on-boarding is probably the hardest compared to any other editor. There are maybe some other aspects involved for some people (like lisp vs viml) but those can safelly be ignorred as non important in majority of casses.
- belak 10y agoI do agree with the general sentiment here... both emacs and vim are primarily editors. However, it's also worth noting that emacs is much easier to extend and change than vim which is one of the reasons people do so many things in it (hence the "Emacs is a decent operating system lacking only a good text editor" joke). Handling email, chat, all git operations and more is common in emacs, but fairly rare (at least in comparison) in vim. There's also spacemacs (for a large config) and evil-mode (if you want to get into the nitty gritty details) for using vim bindings in emacs. Doing the opposite would be a much harder feat. I love both editors... and there's a reason I have both a vimrc and an init.el. vim has the advantage of being pretty much everywhere (so it works really well when editing on servers), and has awesome modal editing, but emacs works really well for local development where I can make sure I'm using the right version and have it tweaked to work exactly how I want. I don't think that one is better than the other, just that they have different use cases.
- massysett 10y agoBecause Emacs has modes that make it mimic Vim, it's false that Vim "must be better," especially when Emacs can do things (like frames) that Vim cannot. I'm not saying Emacs is "better," just that this line of analysis is flawed.
- majkinetor 10y agoIts not flawed. The greatest use case for editor is editing text. Even the small differences in efficiency in the main use case pile up enormously on the long run. Thats why people practice vim golf - to make micro optimizations that will lead to huge benefit. The argument emacs can do frames is irrelevant in this respect.
- massysett 10y agoYou suppose that the only measure of efficiency is keybindings. It is not. For me, other aspects of the editor, such as frames, superior auto-completion, and superior compilation mode, make me more efficient. I don't use an editor solely to "edit text." I'm using to to accomplish a bigger objective, such as creating or fixing a program. Overall, Emacs is better at that, and the fact that I can give it bindings that mimic those in Vim also helps.
- jcoffland 10y agoActually, the author claimed to be more familiar with vi or rather that they were using vi much more yet decided to go with emacs. Pretty much the opposite of what you are saying.
- erikpukinskis 10y agoNo in the realm of plugins, which was the subject of the article, it's exactly how OP says: they know the Emacs plugin landscape and not the Vim one. For the relevant passage search "I'm not that person".
- jcoffland 10y agoFrom the first paragraph of the article: "The reality is that I already spend most of my editing time in vim"
- dozzie 10y agoI read his blog regularly, and my impression is that cks actually feels more familiar with Emacs, though he uses vi-descendants a little more due to how easy is to deploy Emacs plus all the configuration in all the OSes he runs (times the servers he runs, as they don't have much of a configuration management system).