Slashdot Mirror


Vim Beats Emacs in 'Linux Journal' Reader Survey (linuxjournal.com)

The newly-relaunched Linux Journal is conducting its annual "Reader's Choice Awards," and this month announced the winners for Best Text Editor, Best Laptop, and Best Domain Registrar. Vim was chosen as the best editor by 35% of respondents, handily beating GNU Emacs (19%) Sublime Text (10%) and Atom (8%). Readers' Choice winner Vim is an extremely powerful editor with a user interface based on Bill Joy's 40-plus-year-old vi, but with many improved-upon features including extensive customization with key mappings and plugins. Linux Journal reader David Harrison points out another great thing about Vim "is that it's basically everywhere. It's available on every major platform."
For best laptop their readers picked Lenovo (32%), followed by Dell (25%) and System76 (11%). The ThinkPad began life at IBM, but in 2005, it was purchased by Lenovo along with the rest of IBM's PC business. Lenovo evolved the line, and today the company is well known as a geek favorite. Lenovo's ThinkPads are quiet, fast and arguably have one of the best keyboards (fighting words!). Linux Journal readers say Lenovo's Linux support is excellent, leaving many to ponder why the company doesn't ship laptops with Linux installed.
In February readers also voted on the best web browser, choosing Firefox (57%) over Chrome (17%) and Chromium (7%). And they also voted on the best Linux distribution, ultimately selecting Debian (33%), open SUSE (12%), and Fedora (11%).

195 comments

  1. Oh boy! by Bearhouse · · Score: 4, Funny

    It's popcorn time!

    1. Re:Oh boy! by Anonymous Coward · · Score: 0

      Lenovo's Linux support is excellent, leaving many to ponder why the company doesn't ship laptops with Linux installed.

      When someone pays Lenovo to install a ton of useless crap that runs on Linux, then you'll see a laptop that ships with Linux pre-installed.

    2. Re: Oh boy! by Anonymous Coward · · Score: 0

      but but, i thought emacs could emulate vim?

    3. Re:Oh boy! by ourlovecanlastforeve · · Score: 1

      In this basement! A man weighing in at almost 400 lbs who hasn't seen the sun since 2004 when a kid accidentally wandered onto his lawn!

      And in this basement, Linus Torvalds, who treats everyone who writes code for him so badly that they're terrified to check in patches!

      It's the battle of the aspies!

      Who will come out on top? Nobody! And who gives a shit, really! Nobody!

    4. Re:Oh boy! by grcumb · · Score: 1

      It's popcorn time!

      TOTALLY UNFAIR!!!!

      The vote was shut down before all the votes were cast! Vim users were all :wq while the EMACS users were still trying to press EXT_META_ALT_CTRL_SHIFT.

      We demand an immediate re-vote. Just as soon as EMACS finishes loading.... so... June 2020... I think.

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    5. Re:Oh boy! by Anonymous Coward · · Score: 0

      Nice to read but not much real: Vim is an editor, and the survey is about text editors. Emacs is an OS and few people invest time in learning it simply because they are too much inhabited to "modern" (Windows-like) OSes that they can't understand that other model are possible and many of them are far superior to the actual mainstream.

      If we push FOSS in universities, seriously, perhaps things changes, non by 2020 but perhaps by 2050...

    6. Re: Oh boy! by unixisc · · Score: 1

      Precisely! How does one compare a text editor to a full blown shell emulator? Next they will be comparing Google to Facebook. Oh, wait!

  2. To paraphrase... by Anonymous Coward · · Score: 5, Funny

    vim is great because it's on all platforms is like saying anal sex is great because it works on all genders.

    1. Re:To paraphrase... by Anonymous Coward · · Score: 0

      Besides, nano is just as portable and much much better

    2. Re:To paraphrase... by VAXcat · · Score: 1

      And easier to use.

      --
      There is no God, and Dirac is his prophet.
    3. Re:To paraphrase... by Anonymous Coward · · Score: 0

      It is true that nano works on all genders, though I would not say it is better than anal sex.

    4. Re:To paraphrase... by ShanghaiBill · · Score: 4, Insightful

      And easier to use.

      Not easier to use. Just easier to learn.

      You can learn to ride a tricycle easier than a bicycle. But you aren't going to win the Tour de France on a trike.

    5. Re:To paraphrase... by Hallux-F-Sinister · · Score: 1

      vim is great because it's on all platforms is like saying anal sex is great because it works on all genders.

      I think vim is better because you don't need a functioning control key to do stuff, just an escape key, and a working colon button... for example, the commands to abandon a document and exit without saving, and the one to save and then exit are esc-colon-q, (with a "!" character, if changes have been made since last save, of course,) and esc-colon-x, respectively. With emacs, everything is control-this and control-that, which all kidding aside, means that vim is not just more portable in terms of what it will work on, but also in terms of what kind of keyboard or keyboard emulation you need to work WITH it, and also if your terminal emulator grabs or intercepts the control key, it won't hamper you or require special settings, since you don't need to use the control key in vim.

      Hey... I just realized, with vim, you can escape the colon, while emacs is preferred by CONTROL freaks!

      XD

      --
      Our reign has gone on long enough. Indeed. Summon the meteors.
    6. Re:To paraphrase... by ls671 · · Score: 1

      I use Joe's Own Editor or vi/vim on systems where it's not installed.

      I feel home with Joe's Own Editor because it is similar to what I used to use in the '80s with Borland "turbo" environments.

      I have always found pico too simplistic although as you said, it isn't that hard to use.

      JOE is a powerful ASCII-text screen editor. It has a "mode-less" user interface which is similar to many user-friendly PC editors. Users of Micro-Pro's WordStar or Borland's "Turbo" languages will feel at home. JOE is a full featured UNIX screen-editor though, and has many features for editing programs and text.

      --
      Everything I write is lies, read between the lines.
    7. Re:To paraphrase... by arth1 · · Score: 2

      and esc-colon-x

      Or simply ZZ.

      But these arguments are not in favor of vim, they're in favor of the vi family. I much prefer nvi over vim, not the least due to file locking, and also because undo/redo also works on undo/redo like in vi, while vim has this changed. In vi/nvi, you can hit u u and toggle between undo or not. Also, vim lacks the open mode of vi.

      But I'm sure that votes came in for vim because that's the only flavor of vi the the voters knew about. Much like the WTF of more people voting for Chrome over Chromium. Did they actually know the differences, and voted due to that, or did they vote on the only thing they knew?

    8. Re:To paraphrase... by Anonymous Coward · · Score: 1

      Only because the UCI bans recumbents.

    9. Re:To paraphrase... by Anonymous Coward · · Score: 0

      I'm borrowing that!

      Seriously though, how bad were editors pre vi? The UI equivalent of trying to go in via the earhole? Hell the god awful "word processor" rom on my early 80s micro was more user friendly than vi.

    10. Re: To paraphrase... by Anonymous Coward · · Score: 0

      Edlin.

    11. Re:To paraphrase... by Anonymous Coward · · Score: 0

      Fortunately, we can have both :D

    12. Re:To paraphrase... by KiloByte · · Score: 1

      Yeah, jstar (JOE with standard rather than Joseph Allen's keybindings) is the best editor I know. And for someone who coded graphical games in TP3 before learning to tie his shoes, moving to a lesser editor would be hard.

      One downside is that the author sticks to some archaic coding workflow, making sending patches too cumbersome to bother.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    13. Re:To paraphrase... by Anonymous Coward · · Score: 0

      vim is great because it's on all platforms is like saying anal sex is great because it works on all genders.

      well... sex IS great! and so is Vim!

    14. Re:To paraphrase... by jeremyp · · Score: 1

      Our system admin managed to trash a Linux server by editing the pam config file with nano. One of the lines was longer than the width of the terminal window, so nano inserted a hard line feed to make it wrap.

      We got the server back with a Live CD and that was the last day nano was installed on any of our machines.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    15. Re:To paraphrase... by Bing+Tsher+E · · Score: 1

      I prefer vi, which is available by default on a new NetBSD install. You can roll out the install and then jump in and edit /etc/rc.d/rc.conf in a few minutes and your system is up and configured.

      You learn how to use vi in a few minutes, and then you have the tool you need for a lifetime. Unfortunately there are crap systems where there isn't even a real vi binary and it's aliased to some other crap.

    16. Re:To paraphrase... by jrumney · · Score: 1

      Emacs can also be used without a Ctrl key: M-x (aka ESC x) is the only command you need.

    17. Re:To paraphrase... by ls671 · · Score: 1

      One downside is that the author sticks to some archaic coding workflow, making sending patches too cumbersome to bother.

      I was surprised to see that it was still maintained a few seconds ago. Many thanks to Joseph Allen then!

      (JOE with standard rather than Joseph Allen's keybindings)

      Tried it, but I remember Joseph Allen's keybindings feeling more natural to me for some reason compared to default TB config. Of course, I tuned it a bit but very little.

      Syntax
                    joe [global-options] [ [local-options] filename ]...

                    jstar [global-options] [ [local-options] filename ]...

                    jmacs [global-options] [ [local-options] filename ]...

                    rjoe [global-options] [ [local-options] filename ]...

                    jpico [global-options] [ [local-options] filename ]...

      JOE also emulates several other editors. JSTAR is a close imitation of WordStar
                    with many "JOE" extensions. JPICO is a close imitation of the Pine mailing system's
                    PICO editor, but with many extensions and improvements. JMACS is a GNU-EMACS imita-
                    tion. RJOE is a restricted version of JOE, which allows you to edit only the files
                    specified on the command line.

                    Although JOE is actually five different editors, it still requires only one exe-
                    cutable, but one with five different names. The name of the editor with an "rc"
                    appended gives the name of JOE's initialization file, which determines the personal-
                    ity of the editor.

      --
      Everything I write is lies, read between the lines.
    18. Re:To paraphrase... by tender-matser · · Score: 1

      I much prefer nvi over vim, not the least due to file locking

      Then please make noise, maybe someone will finally deign to include some badly needed bug fixes in the upcoming Debian release, especially one related to locking, as well as getting rid of an embarassing security hole someone managed to introduce by blindly messing around with the recovery scripts.

      I have a lot of other bug fixes, especially related to multibyte support, but judging by the reactions, it seems that I'm the only nvi user left on Debian; there's hope, however: someone found it worth his time to make the building of the nvi package dependent on systemd ;-)

    19. Re:To paraphrase... by K.+S.+Kyosuke · · Score: 1

      All that's required for evil to triumph is for good men to do nothing.

      Actually, it would appear that all that's required for evil to triump is to start convincing Vim users to switch to Emacs.

      --
      Ezekiel 23:20
    20. Re: To paraphrase... by Anonymous Coward · · Score: 0

      s/anal/oral/ what's the problem?

    21. Re: To paraphrase... by Anonymous Coward · · Score: 0

      nano -w

    22. Re:To paraphrase... by tender-matser · · Score: 1

      Seriously though, how bad were editors pre vi?

      teco

      Hell the god awful "word processor" rom on my early 80s micro was more user friendly than vi.

      Just like notepad or nano, it was a vi that was always in input mode. A half or quart vi.

      It's very easy to get vi more "user friendly". For instance

      :map! ^[[A ^[ka
      :map! ^[[B ^[ja

      will make up/down arrows work without switching mode.
      (press control-V, esc to enter ^[)

      The difference between vi and eg. notepad is "philosophical"; just like the difference between manual and automatic transmission in cars -- anybody who has learned to drive with the former won't find the latter more "user-friendly" at all, but just stupid and annoying.

    23. Re:To paraphrase... by Dogtanian · · Score: 1

      I wish someone would port it to bloody Emacs then- just about the *only* feature some obsessive hasn't added to that is a decent text editor!

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  3. Sounds all so unamerican. by Anonymous Coward · · Score: 0

    Bob and Alice, where are you now?

  4. Well, of course it does. by Threni · · Score: 1

    It's a better editor.

    Regarding the message "Chances are, you're behind a firewall or proxy, or clicked the Back button to accidentally reuse a form. Please try again. If the problem persists, and all other options have been tried, contact the site administrator." you get when you post a comment sometimes. I wonder if this message has EVER been an accurate description of what's happened, rather than someone who can type, typing a short message then pressing send.

    1. Re:Well, of course it does. by hey! · · Score: 1

      Oh, I'm sure vim is a better editor than emacs, in the exact same sense that a claw hammer is a better tool than a sledgehammer.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    2. Re:Well, of course it does. by Anonymous Coward · · Score: 0

      "It's a better editor."

      No, it really is not. Model fucking editing was a bad joke in 1985 when I first used Vi, and it's still a joke today.

    3. Re:Well, of course it does. by lenski · · Score: 1

      Almost agreed on modal editors:
      Trying to convert from EDT (Digital: RSTS/E and VAX) to vi on joining AT&T B.L. in 1988 was a real challenge. My EDT fingers ruined editing sessions for days until I unlearned the "just type and go" habit.

      Vim's key mapping has improved with the result that many of the control operations (indent controls, selection, movement, including mouse wheel scrolling and ) to work without mode change. It also allows automatic entry of "insert mode" on startup. But vim is not GUI so clicking into a search bar is not available to the best of my knowledge, so it remains old-school.

      For my purposes, the big win for emacs and some other visual editors (jedit) is the ability to create multiple windows. I am surprised by the limited options for my preferred style, which is to have multiple toplevel windows showing and allowing editing in the same file. I still work in C (embedded etc.) and really like having header fragments in one place while actively editing in another, with "instant" switching between them with a mouse click. That can be sort-of emulated in atom and other "splittable" editors, but there are still speed bumps.

      So I prefer emacs and jedit as a result.

    4. Re:Well, of course it does. by Anonymous Coward · · Score: 0

      You can use vim with a GUI. You can use the mouse in terminal vim, if you want. You can have multiple splits or tabs with the same or different files in vim.

  5. Well sure it does by NoNonAlphaCharsHere · · Score: 5, Funny

    Most of the Emacs users are still waiting for it to load so they can cast their vote.

    1. Re:Well sure it does by SuperKendall · · Score: 2

      That joke was funny maybeee back in 1998. Emacs hasn't gotten any more complex while CPU's have increased in power a few order of magnitudes so Emacs is quite the speed demon these days.

      And still more powerful than Vim... I can run Vim inside Emacs after all.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    2. Re:Well sure it does by Anonymous Coward · · Score: 0

      I've never met an outsourced Russian who didn't prefer vi. Clearly we need to appoint a special fisherman, I mean investigator to search out collusion between Putin and Lunix Journal.

    3. Re:Well sure it does by Anonymous Coward · · Score: 0

      Why would I be waiting for it to load? It runs as a server and is always available instantly, even over ssh.

      Oh, I see - you're talking shit because you think you're funny. Never mind.

    4. Re: Well sure it does by Anonymous Coward · · Score: 1

      Whoooooosh.

    5. Re:Well sure it does by Anonymous Coward · · Score: 0

      Do you like that walled garden?

    6. Re: Well sure it does by Anonymous Coward · · Score: 0

      He acknowledged the joke. How is this a whoosh moment?

    7. Re:Well sure it does by angel'o'sphere · · Score: 3, Funny

      Emacs, a good operation system. But it lacks a decent editor.

      Glad you now can run vim on (in) it.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    8. Re:Well sure it does by angel'o'sphere · · Score: 1

      Eight Megs and Continuous Swaping.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    9. Re:Well sure it does by NoNonAlphaCharsHere · · Score: 1

      Eventually Mallocs All Core Storage

    10. Re: Well sure it does by Anonymous Coward · · Score: 0

      Escape Meta Alt Control Shift

    11. Re:Well sure it does by Anonymous Coward · · Score: 0

      Sadly, you can't run Emacs within Emacs. :(

    12. Re:Well sure it does by Anonymous Coward · · Score: 0

      It is the editor of the Beast.

    13. Re:Well sure it does by jeremyp · · Score: 1

      That joke became obsolete when somebody wrote a vi emulation for Emacs.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    14. Re:Well sure it does by Bing+Tsher+E · · Score: 1

      You can install Emacs on a Classic Mac running classic MacOS, then open a shell window and be at the command line on your Mac. You can even traverse directories and use the built in ls command and what-not.

    15. Re:Well sure it does by the_povinator · · Score: 1

      Technically you can run emacs inside emacs. You do `M-x term` and type emacs inside that shell. It works but unfortunately it's very complicated to get the control characters to apply to the correct emacs.

      --
      The .sig is dead, and I believe I had a hand in killing it.
    16. Re:Well sure it does by Anonymous Coward · · Score: 0

      late to the thread, but have we found out which jokes are obsolete now, so we can deprecate them?

    17. Re: Well sure it does by Anonymous Coward · · Score: 0

      I don't think that sound effect means what you think it does. ;-)

    18. Re:Well sure it does by jrumney · · Score: 1

      That joke became obsolete when somebody wrote a vi emulation for Emacs.

      I think somebody had already written a vi emulation for Emacs long before anyone came up with that joke. Emacs today ships with at least 4 vi emulations. The original vi-mode seems to be of unknown origin, with the last change made in 1987.

    19. Re:Well sure it does by Anonymous Coward · · Score: 0

      And still more powerful than Vim... I can run Vim inside Emacs after all.

      Vi emulation in Emacs is horrible, it's almost bad enough to make we want to use Emacs!

    20. Re:Well sure it does by Anonymous Coward · · Score: 0

      Indeed much better, since the 8 or 80 megs are no more almost continuously swapping. Hey, emacs is even usable on a laptop from 2000 (fully loaded with 1GB of RAM and a PATA SSD).

  6. Oh really? by dfn5 · · Score: 1
    Come back to me when Vim can read Usenet.

    alt.vim.die.die.die

    --
    -- Thou hast strayed far from the path of the Avatar.
    1. Re:Oh really? by Chris+Mattern · · Score: 1

      It can't cook my breakfast or wash my car either. I want my text editor to edit text; I'm not particularly interested in it doing everything. I have other tools for that. And who reads Usenet any more anyways?

    2. Re:Oh really? by Anonymous Coward · · Score: 0

      Grep, greps. Sort, sorts. Ed/Vi/Vim, edits. "Does one thing" - the Unix way.
      On the other hand, Emacs tries to: replace the OS, emulate the shell, manage systemd for you, reads from the internet, possibly also writes to the internet, boasts a full email client, PDF reader, non-linear video editor and a PhotoShop-replacement image processor .. and oh yes, throws in a third-grade text editor with commands so obscure they could be an insider joke from the Hitchhikers Guide to the Galaxy. :wq

    3. Re: Oh really? by Anonymous Coward · · Score: 0

      Emacs manages systemd now? The mind boggles, but still. Emacs is now the solution to the systemd problem. The solution in search of a problem finally found one!

    4. Re: Oh really? by Bing+Tsher+E · · Score: 1

      There is no easy bugfix for the systemd malware. You're best off just installing a more correct OS, like one of the BSD unixes.

    5. Re: Oh really? by jrumney · · Score: 1

      Even better is that Emacs gives you a consistent interface whether you are managing systemd, sysvinit or brew. No longer does the Poettering tendency to redefine command-line argument ordering to "improve" on long standing Posix convention need to be an unnecessary burden to the sysadmin.

    6. Re:Oh really? by Anonymous Coward · · Score: 0

      Our information are ultimately text, all text editors handle text, at a very basic level.
      Nano is a kids of 4/5 year's old that can mostly identify letters;
      Vim is a teenager who know how to write from the school;
      Emacs is a professional writer's in substantially ANY field.

      That's why many choose Vim instead of Emacs: LJ readers are not ignorant kids, but only few of them are graduate experts in their field.

    7. Re: Oh really? by Anonymous Coward · · Score: 0

      GuixSD is an advanced GNU/Linux distro, designed to be NixOS without Systemd and an untter DSL.

  7. Vim broken in OSX? by snikulin · · Score: 1

    How to enable color highlighting of source code in Vim OSX bash session?
    Emacs works fine.
    Hight Sierra 10.13.13

    1. Re:Vim broken in OSX? by Snotnose · · Score: 1

      I don't have OSX but on Windows/Cygwin I use 'syntax on'.

    2. Re:Vim broken in OSX? by snikulin · · Score: 1

      in OSX "syntax on" produces different shades of green (in a homebrew bash session)

    3. Re:Vim broken in OSX? by snikulin · · Score: 1

      "colorscheme ron" makes comments very light green.
      That's about it.

    4. Re:Vim broken in OSX? by Anonymice · · Score: 3, Interesting

      Odd, have you actually checked there aren't any other default schemes available? On all of the OSX, Linux, BSD & Cygwin Vims I've used, it's always included a standard pack to choose from.

      http://vimcolors.com/

      https://github.com/flazz/vim-c...

    5. Re:Vim broken in OSX? by TheReaperD · · Score: 1

      Sounds like a Mac problem, not a vim problem.

      --
      "Be particularly skeptical when presented with evidence confirming what you already believe." -
    6. Re: Vim broken in OSX? by Anonymous Coward · · Score: 1

      https://github.com/amix/vimrc

    7. Re: Vim broken in OSX? by snikulin · · Score: 1

      Thanks! This one fixed my problems!

    8. Re:Vim broken in OSX? by x_t0ken_407 · · Score: 1

      I use vim daily on macOS (10.13.13) with 'syntax on' without issue (wish Zsh from macports).

      Oddly enough, I HAVE seen the "shades of green" you describe, but only via an SSH session on a CentOS 5 box (don't ask), so I figured it was bc that OS is horribly out of date.

    9. Re:Vim broken in OSX? by Anonymous Coward · · Score: 0

      Try other color schemes if that one doesn't suit you. There a several subtle settings that affect its usage:

      * Try using a terminal that supports 256 colors, and you'll get better results. I'm not an OS X guy, so maybe someone else can recommend a terminal.

      * Terminal setting should support 256 colors. I just use "xterm-256color" with mine (ie: in bash, 'export TERM=xterm-256color'). That termcap will need to be installed on your system for that to help. I'll leave it to you to figure that out.

      * Open something that would be marked up and recognized. ":set syntax" should return something. For trying out different color schemes, I usually open a program source file (something in C, perl, php, python, java, etc), or just open your ~/.vimrc because it should recognize the syntax as vim (ie:":set syntax=vim").

      * Try different color schemes from within vim using ":colorscheme ", and keep tabbing until you see a name you like, and hit enter to try each.

      * While trying each, also see if telling vim your terminal background is light or dark may change what colors are used from that colorscheme. From within vim, use ":set background=dark" or ":set background=light" to have vim reload the current colorscheme with that set.

      * Try starting your terminal with a different fg/bg color. As an example, for xterm, you can do either of these:

      a) xterm -fg black -bg white
      b) xterm -fg white -bg black ... those will affect how the colorscheme looks, and the affect of the ":set background".

      Some mix of all those will get you to something you think is beautiful and/or very useful. YMMV, but what I use is (effectively):
      * xterm -fg black -bg white
      * export TERM=xterm-256color
      * vim "+set background=light" "+set syntax=on" "+colorscheme darkblue" ~/.vimrc

    10. Re:Vim broken in OSX? by jeremyp · · Score: 1

      Works in vi on Mac Os too.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    11. Re:Vim broken in OSX? by jeremyp · · Score: 1

      :syntax on

      MacOS 10.13.3, zsh 5.3 vim 8.0

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    12. Re:Vim broken in OSX? by jrumney · · Score: 1

      While I do have distant memories of writing my thesis on a Mac Classic's tiny B&W screen, I'd have expected the more modern Macs to support at least 4 bit color monitors by now, but apparently that is not the case. I see you now have a green option, do they also do amber?

    13. Re:Vim broken in OSX? by Anonymous Coward · · Score: 0

      How to enable color highlighting of source code in Vim OSX bash session?
      Emacs works fine.
      Hight Sierra 10.13.13

      Sounds like a hipster developer problem to me.

  8. Well, then. by hey! · · Score: 4, Funny

    I guess that's settled.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    1. Re:Well, then. by Anonymous Coward · · Score: 3, Funny

      Yes, if only we'd thought of this sooner.

    2. Re:Well, then. by K.+S.+Kyosuke · · Score: 3, Funny

      Yes, it's confirmed - Vim is the Bud Light of text editors!

      --
      Ezekiel 23:20
    3. Re: Well, then. by Anonymous Coward · · Score: 0

      Makes ya feel like shit, taste like piss, gives you a massive headache....

      Sounds about right ;)

    4. Re:Well, then. by TheReaperD · · Score: 1

      That was a way better burn than I expected it to be. Well played.

      --
      "Be particularly skeptical when presented with evidence confirming what you already believe." -
    5. Re:Well, then. by Anonymous Coward · · Score: 0

      Great! How about creimer vs. sex? We should probably keep it realistic though.

      MOD DOWN THIS MEANINGLESS CREIMER FECE-POST!!!

    6. Re:Well, then. by Anonymous Coward · · Score: 0

      CREIMER' SUBMISSIONS UPDATE:
      Note also that creimer is trying to regain karma by getting his submissions published as articles on /. so make sure to go to:
      https://slashdot.org/~cdreimer
      https://slashdot.org/~criss69
      https://slashdot.org/~Anonymou...
      https://slashdot.org/~FatCashe...
      https://slashdot.org/~ILoveFat...
      https://slashdot.org/~IHateFat...
      https://slashdot.org/~IAteFatC...
      https://slashdot.org/~ITapeFat...
      https://slashdot.org/~IApeFatC...
      https://slashdot.org/~IPrayFat...
      https://slashdot.org/~FatCashe...
      and mod down his submissions as well. The great thing is that you don't even need mod points to mod down a submission, just click on the "minus" icon!

      Yes, believe it or not, creimer owns all the above sock puppet accounts. It is a mystery why Slashdot management tolerates it!

      creimer wrote:

      I don't bother with mod points. I'm doing something much more sinister. It took ten story submissions ? I'll have to double check the number ? to move cdreimer's karma from neutral to excellent without ever being exposed to the capricious mods. Mmmmmwwwwahahahahahahaha!

      https://slashdot.org/comments....

      Danger, Will Robinson, Danger! Creimy is posting more than 2 posts a day. Hurry! mod down otherwise /. will go to hell again!

      Note: you can mod down even if already at -1 to lower karma and to prevent lost /. users to accidentally mod up.

      creimer wrote:

      All you need to do is find a website with a permissive TOS, say, Slashdot, create a Python script to scrape your own comments, sprinkle Amazon affiliate links in various posts, and then re-post past links whenever possible. Won't be long before you start making "coffee money" each month.

      https://slashdot.org/comments....

      C.D. Reimer is a renowned Slashdot collaborator, as he puts it himself; "Because of the quality of my posts and my article submissions, I'm a highly rated commentator and moderator."

      But does anybody ever wondered what "C.D." stands for? Well, it stands for Creimy Dumpty of course!

      Creimy Dumpty sat on the wall,
      Creimy Dumpty had a great fall.
      All the king's horses
      And all the king's men
      Couldn't put Creimy Dumpty
      Together again.

      Creimy's siblings video and theme song, very realistic, especially the pants, just like Creimy's:
      https://www.youtube.com/watch?...

      With "Vice President Pence Vowing US Astronauts Will Return To the Moon", we are sure they will need miracle workers up there, here is what it would look like. Note that Creimy takes care of bringing a lot of food to the moon as depicted below:
      https://www.youtube.com/watch?...

      Creimy's real pictures:
      Before the sex change:
      https://ibb.co/cc7Ddw
      After the sex change:
      https://ibb.co/gVad65

      Creimy's "enterprise-level" chair, he talks about it all the time on slashdot:
      http://www.keynamics.com/image...

      Creimy's head, while his supervisor was talking to him, not with him

  9. Ed is the standard text editor. by zm · · Score: 2

    Nuff said.

    --
    Sig ?
    1. Re:Ed is the standard text editor. by Bing+Tsher+E · · Score: 1
    2. Re:Ed is the standard text editor. by dwye · · Score: 1

      You joke, but I used to work with a woman that learned Unix when ed was state of the art. She complained that ex (let alone vi, vim, emacs, etc.) just didn't come off her fingers like ed.

      She also had her own source license, and for a mere $50,000 (1990 dollars) could have updated it to the modern distribution, so that gave her seeming craziness a bit more cred than the emacs bigots who couldn't even mark a section except by deleting and restoring it.

  10. No Joe's Own Editor? by greenwow · · Score: 2

    Blasphemy. It emulates they keyboard commands from WordStar which the Borland tools also emulated. It's the choice of many old-school programmers.

    1. Re:No Joe's Own Editor? by dwye · · Score: 1

      Old school Messy-Dos programmers (said the ex-TOPS-20 programmer).

  11. Why I never learned to like Emacs by Snotnose · · Score: 1

    Around 1990 or so I started a new job where everyone used Emacs. So I thought I'd give it a shot. I had 2 major problems:

    It was easy enough to fire up the help system. I couldn't figure out how to exit the help system to get back to my work without killing emacs and restarting.

    A lot of the commands didn't work the way the manual said they would. About 6 months after going back to Vi a co-worker said "oh, you never got our .emacsrc (or whatever it was called). Yeah, these folks had a huge config file that changed pretty much all the commands in some way or other, and they'd forgotten to mention it to me.

    1. Re: Why I never learned to like Emacs by Anonymous Coward · · Score: 0

      Great communication skills on your part not asking why the commands didnâ(TM)t work

  12. Ignores the same major issue as emacs: by Anonymous Coward · · Score: 0

    Every version is subtly different, and just because you can use the modern version doesn't mean you know the subset of common features that work everywhere.

    Like how many people remember that old versions of vi didn't support arrow keys at all, and you had to use the jkim(hg?) keys to move the cursor left right up down?

    While it is true some variant of these are available everywhere, just like pico/nano, they can't be relied on to be an iteration of the application you know how to use. Or like jed where the newer version has a traditional style toolbar along the top, instead of the two row bottom one they had throughout the 90s and early 00s, using F10 instead of alt to enter (either of which may need to be used with the toolbar iterations depending on which key passes through your connect chain unmodified.)

    1. Re:Ignores the same major issue as emacs: by techno-vampire · · Score: 2

      While it is true some variant of these are available everywhere, just like pico/nano, they can't be relied on to be an iteration of the application you know how to use.

      That may be so, but nano, at least, puts the most common commands on the bottom of the screen, including the all-important keystroke that gets you into the rest of the help system. Of course, you need to know that ^X means what most people would write as CTRL+X, but anybody who's expecting to need to use an editor in a CLI shouldn't have any trouble with that.

      --
      Good, inexpensive web hosting
    2. Re:Ignores the same major issue as emacs: by angel'o'sphere · · Score: 1

      Hm, my Mac has a ^ sign on the control key :)

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    3. Re:Ignores the same major issue as emacs: by menkhaura · · Score: 3, Insightful

      "Every version is subtly different, and just because you can use the modern version doesn't mean you know the subset of common features that work everywhere."

      You are talking about the many vi clones that exist or existed (nvi, elvis, ex-vi, stevie etc). while the article mentions the One True Editor that came to rule them all, Vim, created by Bram Moolenaar. Today any *nix distribution is guaranteed to have vim available, and there is no such difference of common features anymore.

      --
      Stupidity is an equal opportunity striker.
      Fellow slashdotter Bill Dog
    4. Re:Ignores the same major issue as emacs: by Dutch+Gun · · Score: 2

      I had to work remotely on some Macs on my last job, and only had a terminal interface via SSH. nano was my editor of choice. It was there, and reasonably simple to use for what I needed. So, yeah, I agree its ease-of-use is a bonus. I'll typically just fire up nano for editing small text or config files if I've already got a terminal open, but for actual programming work, I tend to use an IDE.

      I'm not sure I understand the logic of people who argue about "efficiency" though, at least when it comes to programming. In my experience, writing good code isn't about furiously typing as fast as you can, so I've never felt motivated to learn a bunch of keyboard-only shortcuts.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    5. Re:Ignores the same major issue as emacs: by Anonymous Coward · · Score: 0

      You are talking about the many vi clones that exist or existed (nvi, elvis, ex-vi, stevie etc). while the article mentions the One True Editor that came to rule them all, Vim, created by Bram Moolenaar. Today any *nix distribution is guaranteed to have vim available, and there is no such difference of common features anymore.

      Actually, the first thing I do on a newly installed system, is to turn off all vim specific features - this is my ~/.vimrc:

      set t_ti= t_te=
      set compatible

      It's actually the last line that does it - the first line tells it to not blank the screen at exit. I really, REALLY, can't live with an editor that colorises my code so it looks like the cheaper end of the red light district, and I despise the cutenesses and the way it tries to be 'helpful'. But to its enormous credit, you have the option to turn it all off.

      IMO, all the features that make vim so very useful, were there already in the old vi; the rest is just fluff.

    6. Re:Ignores the same major issue as emacs: by menkhaura · · Score: 1

      I got used to features such as visual mode, folding and multiple split windows (GP could try :sp, :vs, and C-W w, C-W h, C-W j, C-W k, C-W l etc). Love those fluffs.

      --
      Stupidity is an equal opportunity striker.
      Fellow slashdotter Bill Dog
  13. Well ... by Anonymous Coward · · Score: 0

    Most emacs users just ignore surveys.

  14. Seems I am the odd man out with "Joe". by gweihir · · Score: 2

    Because I usually use "Joe", because of the WordStar compatibility, as I learned coding with Turbo Pascal and Turbo C. I used Emacs for a while until the devel team there made some really stupid decisions, then I went back to Joe. So far it has compiled anywhere I tried and usually just works.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:Seems I am the odd man out with "Joe". by bobby · · Score: 1

      I'm very surprised Joe isn't high on the list. Joe is on every Linux system I touch, and not because of WordStar, I'm not sure I ever used WordStar. I just find Joe easy to learn and use, small, fast, etc. I use vi when I have to, probably used ed a long time ago, tried emacs- yes it's great but I don't need all that just to edit a simple config file. Joe does great syntax highlighting, btw. I use nano sometimes also, mainly because I used to use Alpine (aka pine).

    2. Re:Seems I am the odd man out with "Joe". by Zerc · · Score: 0

      I am another joe user,also because I learnt the keystrokes from Turbo Pascal. The only minor irritation is that it is not part of the standard repositories in CentOS/Redhat.

    3. Re:Seems I am the odd man out with "Joe". by bobby · · Score: 1

      I always find Joe. I think it's in the epel repositories. Or maybe elrepo, or ius? Either way I normally just grab the joe rpm and install directly.

    4. Re:Seems I am the odd man out with "Joe". by gweihir · · Score: 1

      I had that "no Joe" problem recently in Solaris 10 (don't ask). Was not problem at all to compile it from sources.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    5. Re:Seems I am the odd man out with "Joe". by gweihir · · Score: 1

      It has a very simple and resilient installation (like good software should have), so that should work almost always.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    6. Re:Seems I am the odd man out with "Joe". by Anonymous Coward · · Score: 0

      I started using JOE when I was introduced to DEC alphas running unix (1995?). It is both simple and powerful. I don't need cheat sheets. If I need even more powerful text editing, I will use sed.

  15. Both are terrible editors IMHO by Solandri · · Score: 0

    VI's interface design was crafted to overcome the lack of a mouse and arrow keys on most computers back in the 1970s and 1980s. It's totally unnecessary today, and having to artificially switch between edit mode and cursor movement mode needlessly slows you down.

    Emacs is way too reliant on the ctrl key. In grad school where we were encouraged to use emacs, I developed RSI in my left hand (pinky) from having to hold down ctrl so often when typing. Eventually I developed a habit of jamming it down with the side of my palm, but it's far from ideal. Alt is a better modifier key for repeated use IMHO, as your thumb on the space bar already sits next to it and you only have to curl the thumb a little to press it. I suspect the choice of ctrl as the modifier dates back to the 1970s when ctrl was typically positioned where caps lock is today.

    These are the sorts of long-embedded user interface design choices I wish designers would challenge. Not useless and harmful stuff like flat UIs which slow you down and replacing informative text menus with a generic hamburger icon which simply adds an extra click to every menu navigation operation.

    1. Re:Both are terrible editors IMHO by UnknownSoldier · · Score: 1

      > VI's interface design was crafted to overcome the lack of a mouse and arrow keys

      You are doing it wrong.

      CONSTANTLY moving your hands off the home row to/from the arrow keys is S-L-O-W. Once you learn how to navigate the cursor it is trivial to whip around the screen using only the keyboard.

    2. Re:Both are terrible editors IMHO by angel'o'sphere · · Score: 1

      Unfortunately the non arrow key moving is so counter intuitive that many people never 'acquire' it.
      And honestly, how much slower is moving the hand to the arrow keys anyway?
      I soent my time thinking while I move my hands ...

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    3. Re:Both are terrible editors IMHO by Anonymous Coward · · Score: 0

      It's not the time of moving to the arrow keys or mouse it's falling out of the linguistics of vi operations.

      http://stackoverflow.com/a/1220118

      "If you only understand basic up, down, left, and right cursor movements then vi will be no more productive than a copy of "notepad" for you."

    4. Re:Both are terrible editors IMHO by UnknownSoldier · · Score: 1

      > the non arrow key moving is so counter intuitive that many people never 'acquire' it.

      There definitely is some truth to that. That's why I changed my keybinds to use IJKL because HJKL doesn't work for me and I imagine it sucks for a lot of people too.

      > And honestly, how much slower is moving the hand to the arrow keys anyway?

      You'd be surprised. Quite a bit. It all adds up. Press v, and want to select ...

      * ... end of word alphanumeric only? Press w.
      * ... end of a word all chars? Press e
      * ... beginning of word alphanumeric only? Press b
      * ... beginning of word all chars? Press B
      * ... up-to but not including some character? Press t
      * .. up-to and including some character? Press f

      With the arrow keys you are constantly dicking around pressing them.

      I found this Vim Cheat Sheet to be quite a handy reference.

    5. Re:Both are terrible editors IMHO by angel'o'sphere · · Score: 1

      The question was about hjkl versus arrow keys.
      Not about e, B, w etc.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    6. Re:Both are terrible editors IMHO by Billly+Gates · · Score: 1

      According to Bill Joy the father of BSD Unix and author of Vi was the reason it has the modes is he had a 300 baud modem at his home in Berkeley to the Univerisity PDP-8. It was to conserve bandwidth on the very slow connection.

      But it beat using ed and cat which would be hard and slow on large files on his terminal and 300 baud speed connection.

      He mentioned Emacs must have been great that RMS and others at MIT had fiber connections and powerful hardware at his disposal which he did not have.

    7. Re:Both are terrible editors IMHO by UnknownSoldier · · Score: 1

      You are missing the entire point.

      WHY do you even use the arrow keys in the first place?

      Because cursor movement is step ONE in doing _x_.

      In step TWO you are either:

      * Adding Text
      * Deleting Text
      * Pasting Text
      * Selecting Text

      The arrow keys are a means to an end.

      By keeping your hands on the keyboard the _entire_ time you minimize the time for BOTH steps. THAT's the Vim advantage.

    8. Re:Both are terrible editors IMHO by angel'o'sphere · · Score: 1

      I use the arrow keys like every one else:
      to move the cursor.

      And the arrow keys belong to the keyboard, so no idea what you are talking about.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    9. Re:Both are terrible editors IMHO by UnknownSoldier · · Score: 1

      Moving your hand off the home row to the arrows keys is a complete waste of time.

    10. Re:Both are terrible editors IMHO by angel'o'sphere · · Score: 1

      As I mentioned in another post: 90% of my time I spent with thinking.
      If I could speed up my typing by 100% it would be a 5% net gain.

      Close to pointless.

      And as I pointed out also in another post: using h j k l is counterintuitive. I can not memorize those keys.

      And obviously moving my hand from j k to the arrows happens so rarely that the above 5% gain most likely would only be a 5 per mil gain ...

      But be free to think otherwise ... I have again to think about what I actually want to write ... :D

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    11. Re:Both are terrible editors IMHO by UnknownSoldier · · Score: 1

      _Your_ myopic use-case of 90/10 doesn't apply to everyone. You could use Notepad and you would still be just as "productive."

      So Vim provide zero benefit _for you._ Great. But only an fool keeps ignoring the answer when people say _why_ Vim is the better solution for _their_ needs.

      We see other people coming to the same conclusion:

      it was voted the most popular editor amongst Linux Journal readers; in 2015 the Stack Overflow developer survey found it to be the third most popular text editor; and in 2016 the Stack Overflow developer survey found it to be the fourth most popular development environment

      I tried Vim out in the early 90's. I hated it. Back in 2010 I forced myself to use only Vim for one month. The learning curve is a fucking vertical wall, but once you get over it, you will never look at any other text editor the same way again. My only regret is that I didn't learn it 20 years early.

      For the rest of us where our time is split closer to 10% thinking / 90% typing Vim significantly cuts down on the iteration time -- we think and almost instantly our changes are applied which frees us up to repeat the cycle. That's a HUGE productivity boost for us professional programmers.

      It sounds like all you do is mickey-mouse "one-off" text editing and never do any advanced text editing.

      The ability to repeat (almost) ANY command just by typing in a number before the pressing the operation key shows why every other editor is crap.

      * Want to delete 16 chars, type 16x.
      * Want to insert 16 spaces, I type: 16 SPACE because my space is mapped to: i SPACE ESC l -- due to inserting spaces being is one of the most common operations.
      * Want to insert N columns of spaces? Press Ctrl-Q to start block select mode, type a number, press k to move down, press y to copy, type a number, press p to paste.
      * Want to record a macro? Press q, give it a single letter name, type your keypresses, and press q when done. Want to play it back N times? Type in the number, press @, and the macro name. Every other text fucks up this simple operation and make it more complicated then it needs to be.

      Plus I can use the same editor, with the same configuration, across Windows, OSX, and Linux. I don't have to use some shitty text editor that only works on one OS, nor use some slow, bloated IDE that only works on another OS.

      Vim also comes with a built-in diff tool. You can see 2-way and 3-way diffs AND edit them. It sounds like you have never had to manually merge code.

      Constantly complaining about hjkl just shows you are not interested in putting the time in to learn it and would rather just make excuses. Gee, if only there was an option to remap keys ... oh wait, there is!

      When I first started learning Vim I started re-mapping every key to better match what I "thought" it should be. It took me about 2 weeks but then I realized that _every_ key in Vim was chosen for a _specific_ reason. The entire key mapping is synergistic -- everything fits together in a logical fashion. You will NEVER understand this until you actually USE it.

      Vi / Vim was written by programmers for programmers. It sounds like you are either still an amateur or spend more time managing then programming -- Notepad or Notepad++ does everything _you_ need. But for us professionals who deal with text day-in, day-out, Vim is literally a no-brainer once you learn it.

    12. Re:Both are terrible editors IMHO by angel'o'sphere · · Score: 1

      Rofl,

      you still don't explain to me, why hitting ESC, j, j, j and then i again should be faster than just using the down arrow instead of leaving insert mode and getting back into it ...

      Yes, vim is an editor for programmers, that is why I use it mostly under unix. However 90% of my editing time I do in a modern IDE. Vim I only use for bash or awk scripts or the occasional other text file I stumble over.

      If you spent so much time typing and not thinking, you most likely do it wrong anyway ... work smarter, not harder!

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    13. Re:Both are terrible editors IMHO by UnknownSoldier · · Score: 1

      > you still don't explain to me, why hitting ESC, j, j, j and then i again should be faster than just using the down arrow instead of leaving insert mode and getting back into it ...

      1. Gee, if only you could learn to read.

      2. You DO realize you can hit Ctrl-C instead of ESC, right? Pressing ESC is slow.

      3. A vim user wouldn't be pressing j 3 times, they would be typing: 3j. They might even type: {LineNumber}g. Which brings me to my next point:

      4. You're ignoring the context. WHY are they moving the cursor 3 times? WHAT are they changing 3 lines down? You are focusing on "one-off" edits; when you focus exclusively on a single tree you are missing the ENTIRE forest.

      There is a reason Vi/Vim has two modes: Command Mode and Insert mode. Because when you are command mode chances you are will be doing _more_ commands. And when you are insert mode chances are you will probably be doing _more_ inserts. Vi/Vim is optimized for the _common_ case -- not the uncommon case of switching command-mode / insert-mode / command-mode.

      If you actually paid any attention to writers you would notice they go through a similar process. In phase 1 they just _write_ -- spelling mistakes included. THEN they go back and cleanup spelling, grammar, re-arranging words / sentences / paragraphs.

      Other editors suck -- because you have to hold ADDITIONAL keys down to do commands, such as Ctrl-Arrows or Ctrl-Shift-Arrows to select text. How do you select up-to-and-including a character in this dumbed-down selection mode? How do you select up-to-but-not-including a character in this selection mode?

      With Vim, when you are command mode, you only need to press a single key: a-z.

      > If you spent so much time typing and not thinking, you most likely do it wrong anyway ... work smarter, not harder!

      Incorrect. Just because _your_ brain is slow doesn't imply everyone else's is. Come back when you've been programming for 40+ years and have most of the code "in your head."

      If all you are doing is "one off" edits, then stick with Notepad. For any one doing anything serious in their craft, they pick up professional, specialized, tools. Vim is a text editor for professionals, not amateurs.

    14. Re:Both are terrible editors IMHO by angel'o'sphere · · Score: 1

      I don't know why you want to praise the merits of vim to me.
      I told you already when I work on the CLI, I use vim exclusively.
      And I hit ESC, because my left pinky easy reaches it, CTRL-C are two keys that are awkward to press.

      I use vi and now vim since 30 years, do your rant is completely pointless.

      Proposing Notepad, even its SuperNotPad variations make you look ike an idiot. It has no single command vim has ... probably not even a regexp search and replace. Also: it does not run on unix. It only runs on windows as you probably know, so how exactly do you think I edit a file via SSH with Notepad?

      Again: moving my hand from the home row to the arrow keys is not slow at all, costs me perhaps 1/20th of a second ... less than hitting ESC or CTRL-C and then going back to insert mode.

      BTW: I program _professionally_ since 35 years ... and the code I write is always new ... so there is not much as of a template in my head. If I had a template I would probably use m4 instead of typing, or PERL.

      Most other work is Java and C++, for both a simple editor like vi/vim (even with ctaggs) is completely unsuited. But I guess you hate both such languages :)

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    15. Re:Both are terrible editors IMHO by angel'o'sphere · · Score: 1

      Ah. I forgot to adress point 3)
      I knew you would give that braindead answer, when I made my previous post.

      It is faster to type j 3 times than first to count the lines and then decide to type 3j.

      Everyone uses [line number]g when he knows the line number and it is more than a few lines away. No idea why you want to teach/preach no brainers, when they are actually wrong :D

      You do know that you can move around with [ and ] in structured text, like C?

      Anyway, have fun preaching the merits of vim to professioanl vim users, it seems to be important for you.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    16. Re:Both are terrible editors IMHO by UnknownSoldier · · Score: 1

      > Most other work is Java and C++, for both a simple editor like vi/vim (even with ctaggs) is completely unsuited. But I guess you hate both such languages :)

      Out-of-the-box Crap++ is a complete clusterfuck of over-engineering.

      I personally use C++ with ctags -- I will clarify that in a moment.

      When even a C++ committee member admits that they write in a sub-set of C++ you know the languages is b-l-o-a-t-e-d.

      Myself, like many other game developers, such as John Carmack, use something called "Super C" or "Embedded C++" -- basically C++ without all the bloated features.

      * No exceptions
      * No RTTI
      * No References (use pointers)
      * Minimal usage of templates
      * Const everywhere
      * Shallow Class Heirarchy
      * Polymorphism when it makes sense
      * Inheritance when it makes sense

      CppCon 2014: Nicolas Fleury "C++ in Huge AAA Games"
      https://www.youtube.com/watch?...

      And when _another_ person on the committee officially recognizes iostreams' performance is crap and hates it: ... and not so much interest in fixing or somehow superseding iostreams which I hate in all its forms. you quickly realize iostreams' slow performance and over-engineered design will never be fixed.

      In case you didn't notice those C++ morons are STILL trying to add a 2D graphics library -- which would have been fine 20 years ago -- but everyone is either using Direct3D, OpenGL, Vulkan, or some other proprietary piece-of-shit 3D library. We don't need Yet-Another-Graphics library.

      Title: A Proposal to Add 2D Graphics Rendering and Display to C++
      Date: 2018-02-1
      http://www.open-std.org/jtc1/s...

      **facepalm**

      There is no _standardized_ name-mangling -- something that would help solve _today's_ real problems.

      Gee, when are packages coming to C++? You know, something Pascal had 30 years ago???

      I could go on but that's enough.

      Java is an even crappier language. I wrote some CRC32 in version 7 2 years ago -- it was one of the worst programming experiences I've ever had.

      * It took _eight_ revisions to add support for a native unsigned type???
      * Any language that _forces_ only one class per file is brain dead
      * The compiler was brain dead -- it was unable to cast an int to a boolean and short-circuit an IF clause
      * Let me know when there is a way to make the GC _100% deterministic_ AND give it a _hard_ millisecond deadline, or even disable the dam thing. Ignoring memory management doesn't magically make it go away.
      * The extra/long/verbose/path/to/my/source is crap,
      * The gradle/maven build system sucks
      * Verbose languages, like Java and COBOL, suck.

      There is a reason the stereotypical Java-weenie exists.

      .

    17. Re:Both are terrible editors IMHO by angel'o'sphere · · Score: 1

      I agree with most.
      However regarding Java: if you want your own memory management, you can 'disable the GC' in the sense that it only gets triggered when you are really out of memory and manage your 'released' objects in free lists for later reallocation.
      Most embedded JVMs make hard guaranties how much time they spent allocating an object, and use that time for a mini GC period. There are commercial JVMs that have similar options, or run on custom hardware which is much faster than an x86 anyway.

      The idea that you can assign an int to a boolean is deliberatly not in Java (and its sister languages), so bugs like this can not happen:

      if (a=b) // should be == ....

      Of course a matter of taste, I like it though.

      Maven sucks, that is true. Some idiots who only had the basic grasp about how to write a build system/build tool invented it and called it maven. Maven as in Magician. Probably the name fits ... magically it somehow works, and no one knows why or how :) And they settled on XML as description language ... but still don't check if the XML is valid ...
      Gradle however I like, it is basically a fancy make file.

      Java does not require one class per source file. It only requires one public class per source file, and of course you can use nested top level classes (via static).

      Yes, being forced to unsigned ints is/was extremely limitating. I once wrote a kind of SWEET16 emulator (same idea, but different hex codes for the instructions), it was a pain in the ass ...

      I mean in C/C++ it would have been a quick hack, so it took me 4 days (but it includes a goovy DSL for the mnemonics to have a kind of real assembler)

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  16. I've been using VIM for 20 years by Barefoot+Monkey · · Score: 5, Funny

    I've been using VIM for 20 years.

    I swear one of these days I'll figure out how to quit the damn thing!

    1. Re:I've been using VIM for 20 years by Anonymous Coward · · Score: 0

      Are you one of those people who didn't realize that when the tutorial said to tap the colon, they were talking about the keyboard?

    2. Re:I've been using VIM for 20 years by Anonymous Coward · · Score: 0

      :q, or :wq if you want to save. Those are the only commands I learned and needed so that I could give myself sudo privileges and install emacs.

    3. Re:I've been using VIM for 20 years by Anonymous Coward · · Score: 0

      Don tell anybody, I'll give you a tip ... Try ctrl-z.

    4. Re:I've been using VIM for 20 years by hcs_$reboot · · Score: 1

      Are we talking about VIM or VIM-within-Emacs?

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    5. Re:I've been using VIM for 20 years by jrumney · · Score: 1
      Whenever I sat down at a system and had forgotten to set $EDITOR before doing a checkin, sending mail or other activities that automatically drop you into an editor, I used to use:
      Ctrl-Z
      killall vi

      But then someone taught me that you can go ESC ESC ESC ESC : q! (apparently one ESC is not always enough, so four or five times is recommended). So mostly I still use my old method.

    6. Re:I've been using VIM for 20 years by jrumney · · Score: 1

      Implementing vim within Emacs is easy. Erik Naggum did it with just one line of elisp.

    7. Re:I've been using VIM for 20 years by starling · · Score: 1

      Here's another one ... Try :x instead of :wq

    8. Re:I've been using VIM for 20 years by Anonymous Coward · · Score: 0

      Wait a minute, it wasn't about anal sex? I've been doing it wrong the whole time?

  17. Linux on the desktop by tomhath · · Score: 2

    The top vote getters for text editor are vim and emacs? That right there tells you why linux will never succeed on the desktop.

    1. Re:Linux on the desktop by UnknownSoldier · · Score: 3, Interesting

      /sarcasm Because in order for Linux to succeed on the desktop you need to run some slow, bloated, shitty ribbon bar IDE right?

      It is obvious you don't deal with text day-in and day-out. Vim works because it becomes an extension of your mind once you learn how to use it. It is FAST. It can edit files of almost ANY size.

      * Linux won in the server space. 100% of the Top 500 supercomputers in the world run Linux.
      * Linux won in the mobile space. Linux runs on over 2 Billion monthly active devices.

      That leaves the desktop space.

      Guess what, no one gives a fuck that Windows dominates the desktop. People _already_ use Linux on the desktop. The only ones complaining about the "quantity" is you.

    2. Re:Linux on the desktop by angel'o'sphere · · Score: 1

      When I have to work under Windows (because 'the PC' runs Windows) I 90% of the time have a linux VM for the real work.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    3. Re:Linux on the desktop by tomhath · · Score: 1

      It is obvious you don't deal with text day-in and day-out.

      My text editing days go back to using SPF on mainframes. Now get off my lawn.

    4. Re:Linux on the desktop by Anonymous Coward · · Score: 0

      Your correct, with either you can be massively productive at the commandline. As the desktop metaphor gets both distorted beyond recognition or function (win10/gnome) or just abandoned (android et al) nvim/tmux in the shell of your choice is becoming more relevant not less.

    5. Re:Linux on the desktop by Roger+W+Moore · · Score: 1

      That right there tells you why linux will never succeed on the desktop.

      No, that tells you the sort of people who already use Linux on the desktop.

    6. Re:Linux on the desktop by Anonymous Coward · · Score: 0

      Most people never use a text editor, they use a word processor. For non technical users like myself notepad or something similar is entirely adequate. I mainly use a text editor to make a list or type information someone is giving me over the phone such as addresses etc.

      Most people who would even bother to look for a text editor with more features than notepad are IT professionals, not mainstream computer users.

    7. Re:Linux on the desktop by Bing+Tsher+E · · Score: 1

      I wrote a lot of code (for an NEC 4-bit embedded controller, in Assembly Language) using Microsoft Word for MS-DOS, but that was because I had one of the only computers in the company, and it was what I had. It worked fairly well.

    8. Re:Linux on the desktop by Anonymous Coward · · Score: 0

      Saying Linux won on mobile is a bit of a stretch. The user-facing parts that actually count in that market are not linux. They're android.

    9. Re:Linux on the desktop by ChunderDownunder · · Score: 1

      Which is why I use Geany.

      It is cross platform, has a decent list of features and has a GUI - I forgot all those vi keyboard sequences 25 years ago. An instructor on Coursera taught his students the dexterous dance of emacs shortcuts but I had forgotten those within 2 weeks.

    10. Re:Linux on the desktop by SurenEnfiajyan · · Score: 1

      Linux won in the mobile space. Linux runs on over 2 Billion monthly active devices.

      Just because the the Linux kernel is used in Android doesn't mean that it's the Linux kernel's merit. It's like to say that 2 Billion cars using a particular engine means that the engine is successful while the original car, the engine is taken from, is lousy. Android is very much different from GNU/Linux, the Linux kernel is buried so deep that most of the developers don't know about it, and it can be replaced with something like this.

  18. Sigh by fahrbot-bot · · Score: 2

    Linux Journal reader David Harrison points out another great thing about Vim "is that it's basically everywhere. It's available on every major platform."

    So is Emacs ding-dong.

    My $0.02 - I'm a long-time Emacs and Vi user - since the mid 1980s. I use Vi /Vim for short/quick edits and Emacs for things I want more of an IDE. Vim is a fine, fairly simple, text editor and Emacs is, well, Emacs. Granted the learning curve for Emacs much higher to really take advantage of it, but it's well worth it over the long run. If I could only have one editor, it would be Emacs - no question.

    --
    It must have been something you assimilated. . . .
    1. Re:Sigh by chthon · · Score: 5, Interesting

      If only because the buffer and windows system from Emacs is still miles ahead of that in Vim.

    2. Re:Sigh by fahrbot-bot · · Score: 1

      And extensibility and Emacs LISP programming capabilities. Perhaps not bit draws for a lot of people, but I've written a bunch of LISP programs for Emacs to help me out with various things (and done coding in LISP as a research assistant, back in college).

      --
      It must have been something you assimilated. . . .
    3. Re:Sigh by Billly+Gates · · Score: 1

      You may want to take a look at what the cool kids use today with electron node.js based editors like Atom.IO and Microsoft Code? There are emacs and vi shortcut packages and the integration and features are amazing and less cumbersome.

    4. Re:Sigh by fahrbot-bot · · Score: 1

      Thanks for the info. I do have 30+ years of experience w/Emacs so it's not really cumbersome for me. I think I'm still pretty cool, or at least productive. :-)

      --
      It must have been something you assimilated. . . .
    5. Re:Sigh by kwerle · · Score: 0

      I know why you use vi for quick edits and emacs for long ones. It's because 30 years ago vi fired up and emacs took its time, right? Same for me.

      Why do you still use vi for quick edits? Launch time is no longer a factor, right?

      I use vi for quick edits and atom for anything more than a line or two...

    6. Re:Sigh by fahrbot-bot · · Score: 1

      I know why you use vi for quick edits and emacs for long ones. It's because 30 years ago vi fired up and emacs took its time, right?

      Not really. I would normally start Emacs and suspend it -- remember, back then it was all VT100 ASCII terminals (or such). I used/use Emacs for development as it was -- and still is -- way more capable and sophisticated than Vi / Vim. The latter are good for making quick, simple edits, like to config files, etc...

      --
      It must have been something you assimilated. . . .
    7. Re:Sigh by kwerle · · Score: 0

      So... can you articulate why you use vi for quick edits? emacs has various vi-modes. So - why vi at all?

    8. Re:Sigh by fahrbot-bot · · Score: 1

      So... can you articulate why you use vi for quick edits? emacs has various vi-modes. So - why vi at all?

      To quote that Almond Joy / Mounds commercial, "Sometimes you feel like a nut, sometimes you don't."

      --
      It must have been something you assimilated. . . .
  19. More evidence.... by Anonymous Coward · · Score: 0

    ... that linux is dying. ;)

  20. Geany... by Camel+Pilot · · Score: 1

    Anyone else here use Geany? With the plugin pack, it is my new favorite. Works the same way on Windows or Linux is another plus.

  21. Vim cleans up by Roger+W+Moore · · Score: 1

    vim is great because it's on all platforms...

    Oh come on. Vim is far more versatile than emacs. Have you ever seen anyone using emacs to clean their toilet?

  22. Or you can install Atom with Minimap and Vim mode by mindmaster064 · · Score: 1

    You then can have them all at the same time. :D

  23. Lenovo? Really? All of em suck at GNU/Linux by Anonymous Coward · · Score: 0

    All three companies Lenovo, Dell, and System76 ship systems that don't work properly under GNU/Linux. The idea that these are the best laptops for GNU/Linux is a fucking joke. Dell and Lenovo both ship systems with digital restrictions that prevent users from installing wifi cards that are actually properly supported under GNU/Linux. System76 routinely ships systems that have all sorts of problems from power management to graphics. The stupidity of Linux Journal readers blows my mind. There aren't many options- but these are NOT good choices. Neither are Apple's Macs or "Purism". I'd go with a 10 year old refurbished Mini Free laptop over any of these companies if nothing else at least these systems have properly supported components in them even if they have a higher failure rate due to age. ThinkPenguin might be another option for something newer. Can't really think of any other companies producing laptops that work well in GNU/Linux that I like.

  24. Lenovo is the best laptop? by eSyr · · Score: 1

    So, those laptops that still, after three model years, don't have Linux driver for a fingerprint reader, those laptops that have a PCIe device whitelist, those laptops that actively prevent installation of a 3rd-party battery, those guys that basically destroyed all good that was in IBM ThinkPads, starting from the keyboard layout and display aspect ratio, have received "best laptop" from Linux Journal? How sweet.

    1. Re:Lenovo is the best laptop? by Anonymous Coward · · Score: 0

      The problem is the entire laptop market sucks right now. Once you look at all the options, you end realizing that the Thinkpad, despite its flaws and being a shadow of its former self, still ends up being one of the best choices out there.

      Though I consider Dell nowadays to at least be Lenovo's equal - if not better than the Thinkpad, as Dell seems to have come a long ways recently, whereas Lenovo's quality has been sliding for some time.

  25. Back in the day there was micro emacs by shoor · · Score: 1

    Back in the 80s, I was exposed to emacs on Vaxen (Vaxes?) which were supposed to be pretty powerful mini-computers, and emacs would noticeably slow them down, whereas vi didn't. However, when I bought an Atari 520 ST, there was no good text editor I could find, until I came across microEmacs https://en.wikipedia.org/wiki/MicroEMACS which I downloaded from Usenet (Ah Usenet in the 80s!) This thing was a very stripped down version of emacs that worked like a charm. Eventually, when computers got fast enough to run emacs I went back to using it now and then, partly because I already had the most commonly used keystrokes in my fingers' muscle memory. MicroEMACS was, and maybe still is, one nice bit of software.

    --
    In theory, theory and practice are the same; in practice they're different. (Yogi Berra & A. Einstein)
  26. Real programmers use... by infosinger · · Score: 1

    This kind of sums up the whole conversation...

    https://imgs.xkcd.com/comics/r...

    1. Re:Real programmers use... by Anonymous Coward · · Score: 0

      My thought on the choice of editor for a software developer is simple: if you're limited by the rate at which you type and edit code - I don't want you anywhere near critical code. Planning, prototyping, thinking, and testing should be taking up the bulk of your time.

  27. Visual Studio Code by Stephen+Chadfield · · Score: 1

    I ditched Sublime Text for Microsoft's Visual Studio Code because Sublime doesn't support Japanese IME under Linux. I use Vim as well for quick stuff.

    1. Re:Visual Studio Code by Billly+Gates · · Score: 1

      Kids today who use node.js electron based editors like MS Code and atom.io can install the VIM add on.

      Really emacs and vim are from a different era in time. They only edit text. Emacs does have some limited integration with GDB but one of the reasons for it's decline and the rise of LLVM/CLANG where better error reporting and ide integration.

    2. Re:Visual Studio Code by dwye · · Score: 1

      Unfair to emacs, which can also edit binary files.

      And the possessive of "it" is "its" -- no apostrophe.

  28. Re:Or you can install Atom with Minimap and Vim mo by Billly+Gates · · Score: 1

    Pft kids today ... get off my lawn you heathen. My gray neckbeard says vi and or emacs are the only editors

  29. Because kids switched to Atom/MS code by Billly+Gates · · Score: 1

    If you do app development and are not very old past aged 30 (sarcasm but semi serious in Silcon Valley) you may find Emacs is not so great with integrating and running tools for Android or web development.

    If you are a system admin you probably use Vim and have no reason to change.

    gcc and gdb too have both gotten a bad wrap after LLVM/Clang came out a few years ago to address issues of error reporting and integration with editors and ides. Other compilers with Atom.io and even Microsoft code with them offer a better development environment than Emacs today.

    Really this debate is from the Reagan era as times are changing.

  30. Win! by Anonymous Coward · · Score: 0

    I like it that we beat SublimeText silly.

  31. In other news...COBOL beats FORTRAN by Tony+Isaac · · Score: 2

    C'mon people! There are so many great editors out there today that are actually modern.

    - Notepad++
    - Sublime Text
    - Visual Studio Code
    - Visual Studio

    These editors can do all the important stuff that vim and emacs could do, and you don't have to memorize a whole list of commands to use them!

    1. Re:In other news...COBOL beats FORTRAN by ebvwfbw · · Score: 1

      Ugh... Really? You really said *THAT*.
      Go to your room without supper. Think about what you typed in here.

    2. Re:In other news...COBOL beats FORTRAN by Tony+Isaac · · Score: 1

      Not sure which part you object to. But yes. Both vi / vim and emacs were developed in the mid-1970s. That makes them about 40 years old. COBOL and FORTRAN are only slightly older. Both of those editors were great in their day, as were the languages. They absolutely deserve a place in our technology museums.

    3. Re:In other news...COBOL beats FORTRAN by ebvwfbw · · Score: 1

      What do I object to? Visual studio, etc... those are all a step backwards. Just because it's microsoft or running under windows doesn't make it better. Now if they supported emacs, well maybe.... but probably not. Microsoft makes stuff that sucks, until they make vacuum cleaners. Then they'll blow.

      I used to code in Cobol and Fortran. Assembler for that matter as well. I don't miss them though sometimes I still have to go all the way down to assembler. They belong in the Museum. Emacs is still very contemporary, vi isn't really. If you knew how to use emacs you'd probably understand why the microsoft stuff is crap. However I have a feeling this is like trying to describe to you what red looks like and you're color blind. You'll never truly understand. As bad as me trying to explain scope, code re-use and objects to a Fortran guy that thought he was doing code reuse in the 1960s. He never did get it. Even after what I thought was very obvious examples.

    4. Re:In other news...COBOL beats FORTRAN by Tony+Isaac · · Score: 1

      Oh, I've used both vi and emacs since the 90s. You don't have to explain. I agree, Emacs is ahead of vi / vim.

      But I wonder if you've actually used Visual Studio. It doesn't even make sense to "support emacs," that's kind of like saying you want Firefox to "support Chrome." Visual Studio is an extremely powerful editor, as well as being a robust IDE.

      Personally, I use a mix of VS and Notepad++, depending on the task. I left vim behind a few years ago when I found that there was no longer any functionality I didn't have in VS / Notepad++.

    5. Re:In other news...COBOL beats FORTRAN by Tony+Isaac · · Score: 1

      OK so I did some googling.

      In Emacs, it seems kind of hard to do things like renaming a variable or function. In Visual Studio, you just right-click the name (any kind of name), choose Rename, type the new name. If there are any conflicts, it warns you. If a class file needs to be renamed as a result, it renames the file and updates the project too. It's smart enough not to confuse names from different modules that happen to be the same.

      Same issue for finding all references to a variable, function, class, or whatever. Right-click, Find All References. The result is not a search, it actually looks at the compiled code to ensure that it lists all, and only, instances of the specific item you clicked, not other items that share the same name.

      When you are debugging, VS automatically shows you profiling info, like how many ms it took to execute each step, or each block of code. It tells you what parts of your code have been covered by unit tests. It's full of shortcuts, like: type "try", hit tab, it creates the try/catch block for you.

      Maybe emacs can do some of this stuff, but I think you'll be hard-pressed to show that it is more powerful than VS.

    6. Re:In other news...COBOL beats FORTRAN by Tony+Isaac · · Score: 1

      And while I'm on a roll, in emacs, while you are debugging, stepping through your code one line at a time, can you make a code change and continue stepping, without a recompile? VS can do that. Can you reset the instruction pointer or change the values of variables in between steps? VS can do that too.

    7. Re:In other news...COBOL beats FORTRAN by Anonymous Coward · · Score: 0

      Yeah, but I don't want to build a machine that needs 8 GB of memory just to edit text.

      Anything that runs on electron is horribly bloated. Visual Studio code suffers from that, as well as NeoVim. Why do I need 200MB dedicated to a text editor?

    8. Re:In other news...COBOL beats FORTRAN by ebvwfbw · · Score: 1

      That guy's problem is very basic. Apparently he didn't know about esc-x,replace-string. From, to, boom! Name conflict? Well if you're a real scientist you don't have to worry about such things. You won't have one because you've already looked. Now this isn't to say that I strongly recommend other people watch what they are doing. People have to kick themselves in the balls a few times to not do dumb things like that. Emacs makes a backup, the filename~ for people that do dumb things. There is also subversion (now git) and even backup tapes if you really did yourself into a hole. Besides, emacs is probably the wrong tool for that. You need an old/new table so you can document it because customers will disagree with what they've told you to do. Then use sed with a big shell loop. Otherwise, what are you really doing? Do you know or are you just changing names? Don't mind me, I've managed people for 30 years and I can spot bad practices a mile away. If you worked for me we'd be having about a 30-90 minute discussion. I've been burned enough times. I used to translate code from things like cobol, fortran, cobol 2 to c, perl, etc. I have a lot of experience with that. One project we had to do over 180 million lines of code. Actually I think it was more than that.

      Can VS split screens and edit two, three, four files all at the same time? Split vertically too. Cut from one window paste into another. I can even create on the fly macros and run them,hell I can even call up a lisp program to do things for you. Yes, there is a useful language named lisp. Can VS do that? Of course not. Not even close. To even suggest what you did shows you haven't used emacs much at all. If you have as you say, you didn't use hardly any of the capabilities. In fact you may have seen the joke that emacs is its own operating system. Even back in the 1980s a guy wrote an emulator in emacs to emulate VI. BTW, I can run emacs on a machine on the other side of the planet. Even over a modem link that is only running at 300 baud with a VT-100 terminal. I've done it, recently. A 300 baud link is all they could get. Try running VS on a machine on the other side of the world with a link like that and get back to me.... If you're still alive by then. Maybe I'll hijack your rdp session... Microsoft is so insecure. Running skype? Yea, I could take over admin on your machine without a problem. They don't even plan on fixing that one anytime soon.

      As for your roll, we were doing that in the 1980s. You know, when Microsoft was in the cave man program loader days. You can even run a shell in an emacs window. Fire it up with make, cc, then fire up gdb and when a problem comes up, pull up that line so you can change it. VS has some of these abilities, however they seem to pale in comparison to a real environment like a Linux/Unix based development environment. Simple things, sure it's great. Simple things for people making simple things type of money.

      I have to use VS for some windows stuff now because the government agency I work for thinks Microsoft is great. I have to cringe because a lot of the ways they have things really suck, at least in my humble opinion. Maybe for you they rock. Even with the abundance of failures with the MS stuff... (like infopath, the old Access, etc). It's ok. For beginners I suppose. I have a nice little job taking the microsoft failures and making them successes under Linux. Usually using a real database like Mysql or Oracle and a real processing language like Python, perl, php, hell I've even been known to use C so I can get to a very basic level and make it run real fast. I don't do java anymore. That's a miserable little language.

      However if VS works for you, that may be all you'll ever need. I hope you're successful with it. A lot of people make a lot of money with it. if you want to really get into stuff, it's not easy. Nothing worth while is. You'll need to learn Linux, emacs, the linux shell - things like awk, sed, tr... these are your basic 1970s technology data processing stuff and I still end up usin

    9. Re:In other news...COBOL beats FORTRAN by Tony+Isaac · · Score: 1

      Well you got me there, I certainly can't run VS over a 300 baud connection! Sounds like it's time for me to get off your lawn.

    10. Re:In other news...COBOL beats FORTRAN by Anonymous Coward · · Score: 0

      Some people prefer to work on the command line, and that basically means vim or emacs.

    11. Re:In other news...COBOL beats FORTRAN by BadDreamer · · Score: 1

      Yes, you do have to memorize a whole list of commands to use them. That you have already done it does not mean that others would not have to do it.

      And no, they can not do all the important stuff that vim and Emacs can do. They can do some of it, and they have some flavor of the month features which nobody has bothered implementing in vim or Emacs, but there are reasons why nobody has bothered.

      Rewriting code while running it sounds like a great idea, until you're running something so complex you actually have use for it, and realize you can't manage the side effects.

      As for refactoring, Emacs was better at that than VS is today before the first version of VS existed.

      Anyway, doesn't much matter, as this is obvious trolling.

    12. Re:In other news...COBOL beats FORTRAN by Tony+Isaac · · Score: 1

      OK, so your approach is to dismiss the VS features Emacs doesn't have, because you feel they are unimportant to you. That's fine, it works for you, but it certainly doesn't show that Emacs is superior. It only shows that you don't care about the newer, more advanced features like edit-and-continue. Personally, those features have saved me many hours of build time!

      And I didn't mention attaching the debugger to an already-running process, including on a remote machine. That's pretty handy when a issues occur only after installation!

      Emacs can do refactoring? Does it actually know where every reference to a variable exists, or is it more like a fancy search-and-replace? Does it know to leave unrelated objects alone, even if they happen to have the same name?

      So you say Emacs can do important things that modern editors can't. Like what, exactly?

    13. Re:In other news...COBOL beats FORTRAN by BadDreamer · · Score: 1

      OK, so your approach is to dismiss the VS features Emacs doesn't have, because you feel they are unimportant to you. That's fine, it works for you, but it certainly doesn't show that Emacs is superior

      It shows Emacs is superior for my needs, which are all I am qualified to talk about. And which you, by the by, are not qualified to talk about.

      It only shows that you don't care about the newer, more advanced features like edit-and-continue. Personally, those features have saved me many hours of build time!

      That tells me a lot about your coding style. Learn to write code and you won't need that crutch, grasshopper.

      And I didn't mention attaching the debugger to an already-running process, including on a remote machine. That's pretty handy when a issues occur only after installation!

      You're right, Emacs has been able to do this since the last millenium, good of you to mention it!

      Emacs can do refactoring? Does it actually know where every reference to a variable exists, or is it more like a fancy search-and-replace? Does it know to leave unrelated objects alone, even if they happen to have the same name?

      Yes, it can do refactoring, and yes, it is actual refactoring and not some kind of fancy search and replace. And it can do it with languages which Visual Studio does not have any support for at all.

      So you say Emacs can do important things that modern editors can't. Like what, exactly?

      I believe that was pretty well covered by another post here, where you decided to be sarcastic because you have never had to work over a 300 bps connection to a user site,

      I have, so I am not sarcastic about the problem.

  32. Nano for the 'win'??? by Anonymous Coward · · Score: 0

    Really guys??? Can we knock off the shit and accept an 'editor' does not need to be an IDE??? Literally 'nano' is about all you will ever have to do if you are doing proper devops, builds and tests.

  33. Vim isn't just an editor by slaymaker1907 · · Score: 2

    Vim is really more a style of keybindings than strictly an editor at this point.

  34. Notepad by Anonymous Coward · · Score: 0

    I worked with a temp/contractor who used Notepad for everything. He knew enough vi to be able to open it, cut/paste from Notepad, and save the file in *NIX.

    vi, i, paste, esc, ZZ.

    Contractors are good at sales, and that's about it!

  35. Beginner vs pro. by ebvwfbw · · Score: 1

    Most people are beginners. When they are more serious and want to be a pro, they learn and use emacs for most of their stuff. I use both, however I use emacs a lot more. Only if I need to fix /etc/passwd or some other small config file where it's just a simple change. Otherwise why use vim? Use a real tool. Even works on the bash command line by default.

    So, doesn't surprise me.

  36. Sir, I Believe You Misplaced Your Goalposts by Anonymous Coward · · Score: 0

    Saying that "no one gives a fuck that Windows dominates the desktop" is pretty funny. Since for years the Linux hordes said exactly that was their goal.

    Once it became clear that Linux wasn't going to achieve desktop dominance, Linux devotees unclenched their anal sphincters and decided it wasn't the end of the world. However there are still plenty around here who will give unwanted, not asked for and inappropriate lectures on the merits of FOSS software. Often to innocent users who simply want to move something from A to B. The same goes in reverse for tirades about Microsoft.

    So claiming credit for what "anyone gives a fuck about" is just retroactive goalpost movement.

  37. Easy reason for me to prefer vi by Anonymous Coward · · Score: 0

    30 years ago we had both vi and emacs. And I even started out as a rabid emacs users. But one simple thing changed that. I couldn't get emacs on any platform - the code wasn't portable enough to port to many of the Unix flavors I used for work, and I couldn't count on emacs being installed by default on any arbitrary vendor's platform. So I picked up vi and learned and threw out emacs. I still remember emacs commands but it's just water under the bridge now. There's no point to going back.

    The other part of it are the interminable macros to install that assure that you will NEVER find two emacs installations that are the same which gets back to the universality of vi and knowing what you are getting and knowing you are getting it.

    I strongly suspect the universal availability of vi or its clones is big part of the preference seen in this poll.