Live data from Hacker News

Sublime Text 2.0 Released

sublimetext.com

341–350 of 358 posts

Re: Sublime Text 2.0 Released

#341

Earlier quoted context omitted.

Same here but with every new Emacs version I can cull a good bit from it. Starting from Emacs 23 it has decreased by at least 50%.

Do you mean it is decreased >= 50% since you started using Emacs 23? What version are you using now?

Yes, sorry to be unclear. When Emacs 23 was released I took a good look at my config and noticed that a lot of things I had added over the years weren't needed anymore.

Looking at the new features in Emacs 24 I expect my config to shrink even more. I am still on Emacs 23 but will switch when it both shows up on Debian Testing and when my workstation needs a reboot.

Re: Sublime Text 2.0 Released

#342

Earlier quoted context omitted.

I use the mouse all the time while developing software. And oddly enough, it doesn't diminish my productivity, since I generally spend more time thinking than typing, and use an IDE to get any boilerplate out of the way or look up API calls or refactor.

Once you are used to an environment where you can do everything with no mouse, it feels very clunky and inefficient when you are in an IDE and you need to constantly switch between typing and using the mouse. If you had to stand up and sit down in order to open a file menu you would think that was silly, but could make the same argument for it that you did for the mouse.

False analogy. Standing up and sitting down does absolutely nothing with regards to file operations.

Re: Sublime Text 2.0 Released

#343
post #316

Earlier quoted context omitted.

Why do you want to use your mouse while coding?

> Why do you want to use your mouse while coding? This reminds me of the times I was tasked with the job of assisting junior programs with their code. At times their mouse usage habits would drive me nuts!!! I would say something like cut those three lines and move them outside of the loop. I would watch them try to mark the three lines of code with the mouse. That would take a second or two. Then they would right cl…

> Five or six seconds later the task was still not done and I would say please move and let me jave a go.

You should probably work on your patience just for the sake of self improvement. That's a little ridiculous.

Re: Sublime Text 2.0 Released

#344
post #292

Earlier quoted context omitted.

>>> "Don't obsess over your tools. They are not the goal" Actually, someone from design background once told me "Good tools produce great work".

I vehemently disagree with this; good tools help get out of the way to allow you to do good work. If your tools are producing work, then you aren't.

Maybe a better one would be "Good tools let you produce great work"?

Re: Sublime Text 2.0 Released

#345
post #326
post #297

Earlier quoted context omitted.

You are arguing against a lost cause. Using a text editor to work with languages like Java/C# was the trend of the 90's. These days 99% of all Java/C# coding is in IDE's. And rightly so, because there is no reason to subject yourself to the torture of programming using an text editor. That sort of verbosity and boiler plate should be handled by tools, not humans. People who code using simple text editors, in highly v…

You're probably right. The last time I touched Java was about 4 years ago. Even then I was using a basic text editor (Eclipse was a monster at the time that took forever to launch and hemorrhaged memory), but it wasn't so bad in the Spring (and Guice) world because you were mostly working with POJOs and didn't need any of the Eclipse autocomplete and refactoring tools. I think the trend will actually go the other way…

I tried to use Sublime for Java (w/ Spring/Hibernate) for a day and found several things I can't live without:

1. Ctrl-1: Automatically tries to fix a compile error. I use this a lot to get my imports automatically, and for other random things.

2. Open Declaration: This was touched on by others and is incredibly useful. The IDE can find the right Class even if two have the same name, while search can make this difficult in some cases.

3. Show References: Similar to above, this is just incredibly useful when you are refactoring or need to see how something is used.

4. Generate getters and setters: I know this one is dumb, but it's so convenient. I just hover over the unused warning then click, and i've got the code.

This editor is snazzy and fast but I don't think I can make the switch.

Re: Sublime Text 2.0 Released

#346
post #339
post #294

Earlier quoted context omitted.

I think his point is right. Market a tool for what it is good at doing. If I want to use vim, I can use vim. Heck there are many things these days that will give you the same GUI candy what GUI based text editors give. Glossy text editors come and go every 2-3 years, Editors like Emacs and vim stay.

On the other hand, what are the odds we're still using them in 100 years? Almost none. The next question then must be: when do we start writing the next generation of tools? Now, or should we wait?

>>On the other hand, what are the odds we're still using them in 100 years?

Firstly you are not going to live for the coming 100 years. So lets not worry about impossible scenarios.

Secondly next generation tools for the next hundred years need to be designed such.

Re: Sublime Text 2.0 Released

#347
post #339
post #294

Earlier quoted context omitted.

I think his point is right. Market a tool for what it is good at doing. If I want to use vim, I can use vim. Heck there are many things these days that will give you the same GUI candy what GUI based text editors give. Glossy text editors come and go every 2-3 years, Editors like Emacs and vim stay.

On the other hand, what are the odds we're still using them in 100 years? Almost none. The next question then must be: when do we start writing the next generation of tools? Now, or should we wait?

The original code for vi was written by Bill Joy in 1976. So, if we applied Gott's Principle and estimated the maximum upside of how long we'll be using Vi or Vi-like editors:

36 years × 39 = 1482 more years of Vi.

Re: Sublime Text 2.0 Released

#348
post #168

Earlier quoted context omitted.

I think, in these days, it is not too much to ask for the intelligent completion, e.g. when you type dot or arrow, to get corresponding members of class/struct - the information is just there and the editor has enough power to parse it... Same goes for a very simple word completion - when the editor already encountered the word in the previous line. These are just _very_ basic things.

But it's not. In fact intelligent completion is incredibly hard for dynamically typed languages. Those IDE that do perform intellisense or autocomplete with dynamic languages do it with very basic ability. In a real world dynamically written code file the editor simply has no way of knowing the members of a class. Or if it is even a "class".

I am still looking for a Perl IDE which offers autocomplete - or at least the option to jump to where the currently selected method is defined. Something like the Groovy/Grails-support in IntelliJ - but of course, Groovy is somewhat easier to autocomplete because of the underlying Java class system.

Re: Sublime Text 2.0 Released

#349

Hm, Am I the only one who spends hours in vim each day with ~15 lines in my .vimrc and almost zero plugins? At some point I think I realized that no matter how feature-rich my editor was, the main thing stopping me from writing good and fast code was _thinking_, not configuring my text editor.

While partly true, the secondary issue is that your editor is inferior to the current state of the art (on all platforms).

I spend most of my time at a black/white board. Once I've won the chalkboard battle, I've put it into motion with chalk, whiteboard markers, and just wrote the computer code. I recommend the latter, though that still leaves a few options open.

For now, I'll let conciseness win.

Re: Sublime Text 2.0 Released

#350

Hm, Am I the only one who spends hours in vim each day with ~15 lines in my .vimrc and almost zero plugins? At some point I think I realized that no matter how feature-rich my editor was, the main thing stopping me from writing good and fast code was _thinking_, not configuring my text editor.

No, thanks
Post reply on HN