Live data from Hacker News

Just Use Sublime Text

delvarworld.github.io

21–30 of 112 posts

Re: Just Use Sublime Text

#21
post #6

> Vim: The Editor You Need To Read (At Least) Two Books On To Use Well No. You need to start using it for 2 weeks and then you can no longer look back on any other editor. You don't need to read two books. Stopped reading the article right there.

I hear ya. I'm currently giving vim a after using Sublime since learning how to code. I'm at the point where I pretty much prefer vim for backend stuff, but I sometimes like Sublime when I'm working on the frontend, especially Angular. I have so many different files in different folders, and I'm just used to being able to get there quickly with Sublime.

You should try Vim Command-T plugin, kicks ass in terms of reaching files quickly.

Re: Just Use Sublime Text

#22
post #4

"For the first 1-2 years of your Vim usage you will be much less efficient than your current editor" years???? This is obviously a typo. If you used a real editor, it'd be quite easy to change "years" to "days."

I don't know, when it comes to navigating and manipulating a single document I can see vim's advantages, but having spend a few days recently trying to learn vim I didn't find any replacements for things like jumping to a file by name or recursive regex searching, things that I've come to rely on in Sublime. Feel free to point out if I missed them, but it seems based on my initial experience with vim that there's not really a concept of a "project" or a "codebase", just the collection of buffers you happen to have open at the moment.

Re: Just Use Sublime Text

#23
"Everyone talks about the steep learning curve but no one talks about what happens once you finally get hjkl in your brain for movement. The answer is months of frustration, followed by finally having a usable editor, followed by knowing some cool tricks that you use in 1% of your daily workflow."

I've seen a lot of people saying this. I've met people who actually experienced this. And I can't listen to it anymore - so I've decided to write a book about how I learned Vim quickly, and how everyone can do this as well[0]. People just don't learn Vim the right way.

There's no need for months of frustration!

When I was starting with Vim, my friends were telling me something like "Just give it a few weeks, and you'll never want to switch back.". However, in every previous attempt to become good at Vim, I would give up after couple of days. Not because I'm someone who give up easily, but because I had lots of work to do.

And with every attempt of switching to Vim, I would spend most of my time on fighting with my new editor and not on the actual work.

The thing is, I didn't have to put so much effort when I first tried Sublime, or when I tried to switch to Textmate. They were downright pleasant.

What my friends were telling me (btw, advanced Vim users), was something like:

- "Turn off the arrow keys, it's not the Vim way..." - "Force yourself to use keyboard all the time, don't use mouse at all!" - "You have to learn x commands, and y things, so you could do z stuff..."

Then I realized - that was wrong! So, in my last (and the succesful one) attempt to switch to Vim (and finally learn how to be productive with it), I decided to don't listen to my "Vim masters" friends. I just decided that in the first couple of days, I'll try to use Vim as any other editor. Just like simple Notepad. No commands, no mappings, no plugins, etc. Just editing text. And that's how it all started.

With using some learning techniques, I've managed to get good at Vim really fast.

For example, if you can't get used to, or you're not productive with h j k l keys for movement, just don't use them. I don't use them. I use arrow keys all the time. Vim "masters" will probably judge me because of this - cause it's not the "Vim way". So what? I don't care. Arrow keys work for me the best, and I'm happy with it.

[0] - I'm in the process of writing a book - Mastering Vim Quickly (from WTF to OMG in no time) link: http://www.jovicailic.org/mastering-vim-quickly/

Re: Just Use Sublime Text

#24
post #17

This is what my Vim looks like. http://www.webhook.com/webhook-uploads/1396995440381_1396021... I'm a designer, not a programmer. I can't code perl, vimscript, and can barely read python or javascript. I can use git repos, which really is all I need to know how to setup Vim properly. That and I guess the ability to read some instructions. I've done nothing more than edit a .vimrc file. It took me a month to switch to…

Whoa, I had no clue you could do all that. Did you follow any guides? I'd love to see my folder structure and be able to switch colors.

Re: Just Use Sublime Text

#25
I just don't get it. The only difference between SublimeText and a GUI version of Vim is that the keyboard shorcuts in SublimeText don't follow the same command/movement patterns as Vim.

And unlike the author, I feel qualified to speak on this as I've been using Vim for 10 years and SublimeText since version 1.

ST is fancy. It's also pricey. I can save you $80 and give you a script that will set up Vim and all the cool plugins you'll need. In fact I've done just that for some of my students.

Re: Just Use Sublime Text

#26
It's the blog post I was born to read. Thank you for writing this.

The amount of stupid tedious pain you're supposed to go through with vi in order just to get a basic working editor is ridiculous. Like some kind of nerdy rite of passage. No thanks.

Re: Just Use Sublime Text

#27
I would recommend Atom over Sublime Text if for no other reason than it being open source. But Atom also has the might of github behind it and a very fast growing community.

I love vim's editing commands: moving through a document, deleting, copying, etc. I think it's by far the best way to edit text. I hate everything else about vim. I find project wide search, finding and opening files quickly, shells and repls inside of vim, etc to all be subpar compared to vim's competition. I'm currently giving emacs with evil mode a try. Although not perfect, it does address most of my vim concerns after using vim for about 4 years.

Re: Just Use Sublime Text

#28

Refreshing to see this after all the Vim gospel programmers out there claiming it's benefits. I do have to say though, I've seen some videos of real Vim pros at work and it's -majestic- how swiftly they move through lines and duplicating lines, editing params, refactoring, etc - a thing of beauty akin to watching videos on /r/artisanvideos[0]. I'll stick to Sublime Text and Nano when I need some ssh terminal editing.…

Our industry works this way and I don't understand why programmers who are always "using the right tool" call anything new that they disagree with "gospel" or "evangelizing."

SublimeText isn't that old. Somehow you found out about it, learned its keyboard shortcuts, found out what plugins to install to do your work, and made it your editor.

That's how I learned Vim. I'll admit that I have a bias, and that learning to use something else would be harder.

But here's the thing - the Vim knowledge I have can translate to Visual Studio with a plugin, to XCode with a plugin, and to Eclipse with a plugin. Netbeans, RubyMine, and Webstorm have a Vim plugin as well.

So does SublimeText.

SublimeText's knowledge transfers to the next paid version of SublimeText.

Re: Just Use Sublime Text

#30
post #22
post #4

"For the first 1-2 years of your Vim usage you will be much less efficient than your current editor" years???? This is obviously a typo. If you used a real editor, it'd be quite easy to change "years" to "days."

I don't know, when it comes to navigating and manipulating a single document I can see vim's advantages, but having spend a few days recently trying to learn vim I didn't find any replacements for things like jumping to a file by name or recursive regex searching, things that I've come to rely on in Sublime. Feel free to point out if I missed them, but it seems based on my initial experience with vim that there's not…

Much of what you're looking for is provided by plugins (eg. command-T).

There's no question that vim requires a lot of messing around with initially to get it configured the way you want it. But that rapidly fades away and it's not such a big investment of time for something as important as an editor.

Post reply on HN