[rapind]

I wasn't using the term "training wheels" in any sort of derogatory way. You described autocomplete as a learning tool to get you up and running fast with a new API. Training wheels seemed like a good analogy. Nothing macho about it.

I don't think autocompleting a call 30 times is nearly as valuable as looking it up for me at least, because since I'm already invested I'll take the time to learn about it. If all I did was tab complete something and it seemed to work I'd be far too lazy to dig any deeper. I don't see why I'd spend any more time on it during consecutive autocompletes either.

Also, when I use a new library chances are very high that I'll be using it over and over and over again. It's more like 10% of APIs that I'll never use again (but still may learn something). I'm speaking purely from experience, and it baffles me that others stated finding so little library re-use. That sounds incredibly frustrating.

It's been my experience having used autocomplete tools in the past (4-5 years ago would be the last time) I don't miss them at all. I don't think they provide me with any real benefits. This is completely thought through and rational IMO. However I will grant you that it's potentially subjective and not everyone would see the same benefits.

[kamaal]

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 verbose and boiler plate demanding languages like Java are exceptional few and going by the trend will never be the norm.

[rapind]

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 though and there'll be less gigantic IDE usage in the future, but I'm not going to put money on it.

[samspot]

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.