Earlier quoted context omitted.
On the other hand this will Github an incentive to keep on improving Atom. Maybe someone has finally figured out how to monetize an editor. I hope so, cause the current ecosystem of editors is a mess of half baked solutions.
Why use one of those half baked solutions when vim already exists?
Git and GitHub Integration Comes to Atom
81–90 of 112 posts
Re: Git and GitHub Integration Comes to Atom
#82Earlier quoted context omitted.
Why use one of those half baked solutions when vim already exists?
I've never actually seen anyone use vim more efficiently than the average programmer can use Sublime Text or Atom with no skill and a mouse pointer. It's just too much required engagement to do things as simple as move to a specific point on the screen or uncomment/indent a bunch of lines of code. Installing plugins is tedious, tabs/buffers/windows are clunky, and memorizing key commands for plugins (like a file tree…
Movement:
Moving around is a hassle at first, most people insist using arrows instead of hjkl, but even thous are slow and tedious. You get much more mileage from using w, e and b for jumping between words, but even thous get slow after a while and recently I've been using the f and t commands to Find and jump To places (characters) I want to. Obviously it requires some time to learn and I am by no means perfect, but I dare to say it is faster than scrolling and pointing with a mouse.
Plugins:
I don't really see how installing plugins is tedious, you just slap one of the managers into your ~/.vim/autoload (I use pathogen) and then rest you just clone to ~/.vim/bundle. Vim doesn't have build in plugin browser and one click install, like Atom does, but at least to me that is not a problem. Maybe it's because I don't use that many plugins, who knows.
Tabs/buffers:
These do take some time to get used to, but I wouldn't say they are any more clunky than your average editors tabs.
Memorizing commands:
At first it seems like insurmountable task since almost every key is a command and as you mentioned most plugins have their own commands, but truth is you don't need most of them to get started and as you use the tool (or at least thats how it was with me) you Google how to do something tedious faster and there is almost always a better method. As for the "file tree view", I don't know what that plugin is, but I can guess and I used something called NERDTree at start, but vim's build in :find command is pretty powerful at just finding what you need and now I use fzf which makes finding files even faster.
Over all I get why you might dislike vim even without trying it (since most vim users constantly push their shitty editor (and dont get me wrong vim is shit, but it's least shit editor I've yet found)), but I suggest you try using it on a side project and see if you like it, don't install any plugins at first just try reading the documentation and making changes to the config as you go along. I bet you'd be surprised how much you'd enjoy it.
Re: Git and GitHub Integration Comes to Atom
#83Earlier quoted context omitted.
I've never actually seen anyone use vim more efficiently than the average programmer can use Sublime Text or Atom with no skill and a mouse pointer. It's just too much required engagement to do things as simple as move to a specific point on the screen or uncomment/indent a bunch of lines of code. Installing plugins is tedious, tabs/buffers/windows are clunky, and memorizing key commands for plugins (like a file tree…
You are obviously entitled to your opinion and it might be that you've only seen people who are still learning to use vim, but to give little perspective from someone who has been using for little over two years. Movement: Moving around is a hassle at first, most people insist using arrows instead of hjkl, but even thous are slow and tedious. You get much more mileage from using w, e and b for jumping between words,…
Why don't I like it as an IDE?
* Second hand auto complete
* Second hand project management
* No debugger
These are actually to me huge features and the third party support for each of them exists but doesn't touch the quality of implementation in a dedicated IDE. Not to mention it adds hours of extra work to getting started in an environment you don't already have configured.
And frankly, you don't have to learn vim to recognize this.
Re: Git and GitHub Integration Comes to Atom
#84Earlier quoted context omitted.
I find bundling Git support with Atom is a requirement, VSCode does it.
Git support is different than a Github bundle. Github is different than Git.
Re: Git and GitHub Integration Comes to Atom
#85Earlier quoted context omitted.
Git support is different than a Github bundle. Github is different than Git.
But atom is made by github, right? Not to justify their choice but you can see from a company perspective how it surely aligns with their goals (increase github market share).
Re: Git and GitHub Integration Comes to Atom
#86I just tried it out and the UX is ridiculously broken for me. Whenever I try to focus one of the Git or Github panes, the content of the panes completely vanishes, since I'm unfocusing the file the content was about.
Re: Git and GitHub Integration Comes to Atom
#87Bundling these features by default is bad for Atom. It changes Atom from an editor to an advertisement. Maybe Github dwarfs the competition but boxing them out of the editor is unnecessary. This smells like bundling IE with Windows 98.
(It's had that button since Azure started)
Thing is, nobody is going to download Atom, see that the GitHub support is built in and say 'oh! Now we're going to have to migrate the team to GitHub!'.
Re: Git and GitHub Integration Comes to Atom
#88Bundling these features by default is bad for Atom. It changes Atom from an editor to an advertisement. Maybe Github dwarfs the competition but boxing them out of the editor is unnecessary. This smells like bundling IE with Windows 98.
to me it smells more like adding a "deploy to Azure" button to Visual Studio. (It's had that button since Azure started) Thing is, nobody is going to download Atom, see that the GitHub support is built in and say 'oh! Now we're going to have to migrate the team to GitHub!'.
Re: Git and GitHub Integration Comes to Atom
#89Earlier quoted context omitted.
Yes once the program is already open it's pretty snappy. But I like to keep my desktop clean so I close / open it fairly often and it's startup time if just not on par I've found.
RAM you're not using is a waste of money ;)
Re: Git and GitHub Integration Comes to Atom
#90Earlier quoted context omitted.
Why use one of those half baked solutions when vim already exists?
I've never actually seen anyone use vim more efficiently than the average programmer can use Sublime Text or Atom with no skill and a mouse pointer. It's just too much required engagement to do things as simple as move to a specific point on the screen or uncomment/indent a bunch of lines of code. Installing plugins is tedious, tabs/buffers/windows are clunky, and memorizing key commands for plugins (like a file tree…