From: Warren Young <wyml@etr-usa.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Vim wins again. :)
Date: Wed, 08 Jul 2015 20:01:00 -0000 [thread overview]
Message-ID: <B51150DF-46D1-452B-BE81-5A1F2CC3E22A@etr-usa.com> (raw)
Those who have been paying attention to the Linux Journal’s Reader’s Choice Awards for years, as I have, watched as Vim continually increased its lead over Emacs to the point that they didn’t even bother asking in the most recent survey. When they asked in 2013, Emacs was at about 10%, behind Vim, gedit, and Kate:
http://www.linuxjournal.com/rc2013?page=44
It is interesting to compare those results to the Stack Overflow Developer Survey:
http://stackoverflow.com/research/developer-survey-2015#tech-editor
You can see the overpowering influence of Windows and OS X here in the top two choices: NotePad++ (blech!) and Sublime Text (yay!).
Sublime Text is greatly improved by the Vintageous plugin, which allows Sublime to emulate Vim so well that I like it far better than gVim.
https://github.com/guillermooo/Vintageous
Although I didn’t much mind paying for Sublime Text as a product, I do worry about it disappearing. Visual Studio Code could woo away enough Sublime users that its developer may simply have to abandon it:
https://code.visualstudio.com/
Thoughts from the other editor geeks here?
next reply other threads:[~2015-07-08 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 20:01 Warren Young [this message]
2015-07-17 12:00 ` Eric Blake
2015-07-17 17:45 ` Warren Young
2015-07-17 18:12 ` Stephen John Smoogen
2015-07-20 15:37 ` cyg Simple
2015-07-22 14:01 ` Robert Pendell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B51150DF-46D1-452B-BE81-5A1F2CC3E22A@etr-usa.com \
--to=wyml@etr-usa.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).