4 ms·

Has this been GH's eventual goal in developing this thing? Playing the long game?

bdcravens 9y ago
The game has changed over time. They originally intended to charge for Atom. Then it became arguably the best free option, until VS Code came along.
- tankerdude 9y ago
  I think a lot of us have moved from Atom/Sublime over to VS Code these days. Seems like lots more momentum and gobs of useful plugins that let me do my work.
  - artursapek 9y ago
    I guess this is the IDE crowd? Us vim guys are still raising eyebrows when people say "best free option" :)
    - chillee 9y ago
      More so the "I want debugging and intellisense without the slowness of an IDE" crowd. :)
    - hobofan 9y ago
      I've been a vim user for a long time. I switched to Atom despite its slowness because I finally get linter and autocomplete integrations that just work. Those have always been a pain to set up for me in vim, and when you are switching between machines all the time, that quickly becomes tiring. I don't see a reason to stick with traditional vim for the majority of my work, since most other editors have plugins with a very good coverage of the core vim features/keybindings. EDIT: Oh yeah, and multicurors. I just remembered that they were also a big part of reason for switching. At least at the time, every implementation of multicursors in vim was broken in a very major way for me.
      - artursapek 9y ago
        Re: multicursors, that's what macros are for.
        hobofan 9y ago
        Sure, you can do most things with macros, but I prefer the interactivity of multicursors. With macros I have to carfully plan out how the macro will affect all the different instances where I let the macro run, and if something goes wrong, I have to revert it and try again. With multicursors I also have to do some trial and error, but usually much less since I can immediately see how each step influences the text at all cursor instances, and revert it in a much more granular way. If I have to do some heavier processing for 100-1000+ lines, I still use macros, but for most cases in my day to day programming multicursors just feel better.
    - bdcravens 9y ago
      I guess I'd say lowest common denominator. As in install in 5 minutes and writing code with no experience crowd :-)
    - tills13 9y ago
      The price is your soul.

The game has changed over time. They originally intended to charge for Atom. Then it became arguably the best free option, until VS Code came along.

tankerdude 9y ago
I think a lot of us have moved from Atom/Sublime over to VS Code these days. Seems like lots more momentum and gobs of useful plugins that let me do my work.
- artursapek 9y ago
  I guess this is the IDE crowd? Us vim guys are still raising eyebrows when people say "best free option" :)
  - chillee 9y ago
    More so the "I want debugging and intellisense without the slowness of an IDE" crowd. :)
  - hobofan 9y ago
    I've been a vim user for a long time. I switched to Atom despite its slowness because I finally get linter and autocomplete integrations that just work. Those have always been a pain to set up for me in vim, and when you are switching between machines all the time, that quickly becomes tiring. I don't see a reason to stick with traditional vim for the majority of my work, since most other editors have plugins with a very good coverage of the core vim features/keybindings. EDIT: Oh yeah, and multicurors. I just remembered that they were also a big part of reason for switching. At least at the time, every implementation of multicursors in vim was broken in a very major way for me.
    - artursapek 9y ago
      Re: multicursors, that's what macros are for.
      - hobofan 9y ago
        Sure, you can do most things with macros, but I prefer the interactivity of multicursors. With macros I have to carfully plan out how the macro will affect all the different instances where I let the macro run, and if something goes wrong, I have to revert it and try again. With multicursors I also have to do some trial and error, but usually much less since I can immediately see how each step influences the text at all cursor instances, and revert it in a much more granular way. If I have to do some heavier processing for 100-1000+ lines, I still use macros, but for most cases in my day to day programming multicursors just feel better.
  - bdcravens 9y ago
    I guess I'd say lowest common denominator. As in install in 5 minutes and writing code with no experience crowd :-)
  - tills13 9y ago
    The price is your soul.