Live data from Hacker News

Just Use Sublime Text

delvarworld.github.com

101–110 of 296 posts

Re: Just Use Sublime Text

#101
post #80

These articles are just idiotic. Mouse as fast as the keyboard except a 'few edge cases'? Get out of here. Vim destroys using a mouse every day of the week, and unless the highest skillset you've learned is fingerpainting, it's not that hard. Sit down for 2 days, stop being a bitch, learn the keybindings, and you're good.

If you need to make a random selection somewhere far away in the text. The mouse was made to do that. Not a multiple keyboard combination. ( I mean "if you're using a trackpad").

For that matter, text selection in general is often better with a mouse.. I'll go either way (sometimes mouse, others keyboard) but I much prefer a gui editor/ide over console UI... when I am remote, I prefer nano, just get it done/save/out.

Re: Just Use Sublime Text

#103

> Vim is Oddly Bad at Indenting Since he mentioned indenting, let me ask: how do you properly indent JSON or XML in Sublime Text 2 out of the box? I've tried setting the appropriate syntax, selecting all text, then doing Edit->Line->Reindent but it gives half-broken results. Is that intentional, or am I doing something wrong? Also, is there a way to quickly select all instances of currently selected identifier within…

Ctrl+D to select the next instance of the current selection.

Re: Just Use Sublime Text

#104
A lot of comments are saying that Vim will massively increase your productivity, but I think that is completely missing what being a productive programmer is all about. Just being able to type and edit things quickly isn't even half the battle, it's less than 1% in my opinion.

Productivity in programming is measured from the time you start a project till the time you finish. So much time is often spent trying to find and fix bugs, and being productive is all about writing code in a way that minimizes the amount of bugs that show up, and being able to quickly find and fix them when they do.

Writing code at the optimal level of generality is a major factor, No amount of editor tricks can make up for choosing the wrong level of generality to write your methods. Too much generality and you are wasting time, too little and you have to deal with a bunch of special cases, or else rewrite large portions of code at some point.

It's important to be able to learn things very quickly on the spot when you have no other choice, but it's better to be able to immediately deal with situations without having to incur all of the productively losses that comes with doing that. So much time is saved by being able to get the algorithm's and the numbers right on the first try.

It's also about a psychological battle of how hard you can push yourself without burning out, which is no trivial matter.

Once you are good at all that, then basically it's nice to also be able to pick up an extra few seconds here and there with a keyboard shortcut, an editor trick, or some precision mouse mechanics.

Re: Just Use Sublime Text

#105
post #83

Earlier quoted context omitted.

As someone who uses a keyboard 98% of the time, but who uses a GUI editor and the mouse when it makes sense, I'd say the mouse is useful for several things, and what it IS useful for WILL be faster than what someone can do with a keyboard. The clear win is using a powerful GUI-based editor that has tons of keyboard commands. Bonus points for being on Windows or Linux (i.e., not Mac OS) so you can navigate/BROWSE the…

Just so you know, in Mac OS you can navigate the menu with keyboard. Try Ctrl+F2 to focus on the menu and then arrow keys

You mean Fn+Ctrl+F2, which requires repositioning both my hands, thus defeating the purpose.

Re: Just Use Sublime Text

#106
some random reasons why I like vi(m):

:'a,.s/, /^M/g

:set no wrapscan ?def n n n (search hit TOP...)

(see word nice down two lines) t t w w (till cursor is at the word 'nice') ctawesome

ma /end :'a,.y a $G "ap

%s/\(^[0-9]\)\(.$\)/\2 \1/

:wq

Re: Just Use Sublime Text

#107

1. I like learning new tools and I got pretty good at vim's 10-15 fundamental commands in probably a couple of weeks. I was certainly OK, albeit a bit slow, by day 2 or so. 2. By the end of month 1-2, vim had become completely second nature. I did stuff without thinking. Actually, thinking about what I was doing started to confuse me. 3. Sure we all spend lots of time thinking, but I also often find myself cranking o…

I have to agree with TFA here... I just don't see the point, and never have. When I'm in an editor, I mainly want to type, and have what I type go in where I type it... I like pico/nano over vi/vim/emacs. I like sublime, but a lot of functionality is only keyboard accessible, and I haven't take n the time to learn hot keys... why I would really love is having my editor, and a couple command/console prompts in the sam…

I don't mean to disregard what you said or insult your approach just because it is different than mine, but I can't tell you how much vim/emacs have boosted my productivity. Not only am I at least 30%+ faster while coding, but in general the process is so well oiled that I have near-0 resistance to just jumping in and getting something done. I jump around in code like crazy, can jump to different files instantly no matter where they are (find-file-in-project), do git stuff (magit), have REPL right there in the editor, replace REPL with some code buffer instantly, set up 4-way split panes and kill them in a split-second, etc. etc.

In my opinion, tooling is very important. You want something that makes you a wizard - something that's smooth and FAST.

I once worked with a very experienced gentleman who preferred Notepad to write 3-page-long SQL queries. He knew his craft very well, got the job done, but boy did he take his time :-)

Re: Just Use Sublime Text

#108
post #25

Am I the only person in the world who: a) Never thought vim was that hard to learn (and I first learned it when I was a teenager and nobody helped me. I switched when someone on a MUD made fun of me for using pico.) and b) Thinks vanilla vim works just fine. Seriously my vimrc is like 10 lines long and I don't even have it on every server I work on. I don't bother with any plugins. I don't need vim integrated with gi…

I'm the same really. I had to learn vim when I started at a games company that had a Linux build chain. I printed out the keyboard quick reference and was reasonably productive after a few weeks. The only plugin we used was ctags, to be able to find shit in our massive C/C++ codebase, but that worked ok (despite having to manually rebuild tags yourself).

I agree with the author - I'd also recommend Sublime Text 2 - but vim fills a great niche - when you only have a telnet terminal, so it's always good to know the basics.

Right tool, right job, etc.

Re: Just Use Sublime Text

#109
post #96
post #61

Earlier quoted context omitted.

Emacs can be pretty pretty--perhaps not actively pretty, but very elegant in a minimalist sort of way. I'm pretty happy with how mine looks[1], for example. [1]: http://jelv.is/emacs-blackboard.png Also, have you tried Evil? Apparently it's a very good Vim-emulation mode for Emacs, highly recommended over Viper.

> Emacs can be pretty pretty--perhaps not actively pretty, but very elegant in a minimalist sort of way. I'm pretty happy with how mine looks[1], for example. Obligatory vim can be pretty too, and I am happy with how mine looks. http://i.imgur.com/ZC2xDxH.png On a related note, I like how my terminal vim looks better than how the GUI looks. I don't use emacs much, but same goes for emacs.

What's your theme, BTW? I also like your custom status bar shape.

Re: Just Use Sublime Text

#110

A lot of comments are saying that Vim will massively increase your productivity, but I think that is completely missing what being a productive programmer is all about. Just being able to type and edit things quickly isn't even half the battle, it's less than 1% in my opinion. Productivity in programming is measured from the time you start a project till the time you finish. So much time is often spent trying to find…

I find it impossible to get anything bang on the first time around. I find that even the best plans and ideas can start to show problems once you get into the guts of the implementation.

Being able to input and edit things quickly greatly reduces the friction involved in doing refactorings. If I can do it fast enough, why not just refactor 3 different ways and see which one makes the most sense?

Also helps with prototyping, being able to from a conversation to a "did you mean like this?" in 30 mins is helpful.

Post reply on HN