Do you deny that you made precisely this incorrect quote: "anyone in front of an IDE is productive"

Obviously tools like cut'n'paste are beyond you. You're also too stupid to realise they don't even mean the same thing. You lose.

And I see you're still waiting for a single person to agree with you.

BTW, I see you are still waiting for a single person to agree with your dumb argument.

You really are an incompetent. Your entire argument is based on a misquote.

You're showing your ignorance again. An IDE is about productivity. You can for example type a complex command in a CLI to do a refactor, but there's no usable interface there to examine preview of the refactor before you do it.

The IDE user leaves you and your primitive tools in the dust.

You're stil not fooling anyone. Your comments are as foolish as a carpenter saying he only ever uses hand tools. When you're learning to be a carpenter, then of course you'll learn to use hand tools. But professional carpenters in this day and age are using power tools for most of their work.

You're not fooling anyone. You gave it away with the lazy slashdot stereotype of StackOverflow. Spending 3 hours on an issue that a StackOverflow search would have found you the key to in seconds is not being a productive programmer. And it's certainly not being a professional one.

You're a poser, not a programmer. You don't do this for a living. You have far too much to learn.

You're obviously an amateur, or someone who works on very small projects.

So you can't.

If your Emacs has all the features of my IDE, then it's an IDE.

Go on then. Demonstrate it.

OK, so you're lucky enough to be writing code from scratch, and you're not working with other people. And you're working on an algorithm in engine code, rather than applications. That cuts down how often you'd want to do it.

That's kind of similar to the students I mentioned that are the classic users of vi.

But in the commercial world, you're usually working on large, complex systems, with a lot of history, usually originally written by other people. And you know it'll be built on still further by other people in future.

IDEs help handle the complexity of big projects. Of which the refactor/renaming rather than search/replace is just one example.

No, using an IDE means you are a productive programmer. I swear most of these vi/emacs hipsters are still students or are unemployed.

This is slashdot, there will always be someone who'll declare they prefer something primitive rather than something more modern and useful.

People using simple editors rarely do. The work and the risk that you'll introduce a bug often isn't considered worth reconsidering the name of a function or identifier. Especially with OO code.

But if you're using an IDE with refactoring support, there's next to no risk, and it's fast. So there's no reason not to rename if clarification is needed, or the code was originally written by someone who's not good at naming things.

I do it quite often.

âoeWeâ(TM)ve learned and struggled for a few years here figuring out how to make a decent phone,â he said. âoePC guys are not going to just figure this out. Theyâ(TM)re not going to just walk in.â

No wireless. Less space than a Nomad. Lame.

I wonder when Apple Watch outsells all Rolex watches ever sold. First for units, then for value.