3 ms·
> Try writing java without an IDE. Why? The availability of powerful IDEs is one of the biggest selling points of Java, arguably topped only by portability an
by thomascgalvin 8y ago
> Try writing java without an IDE.
Why?
The availability of powerful IDEs is one of the biggest selling points of Java, arguably topped only by portability and the large ecosystem of libraries. The fact is, if you're writing Java, you will almost certainly be using tools that help you write correct code more quickly.
And the nature of Java is what makes that possible. The IDE knows what your data means, and it knows if you're trying to do something that isn't allowed. That's the entire point of the article: Java forces you to declare what you're trying to do, the IDE holds your hand through that, and the compiler enforces it.
- agumonkey 8y agoI think it's mostly a fallacy. Static OOP can only do so much, and it's just a cultural side effect that your editor comes preconfigured with JDT. It doesn't help your editor to know what Factory to use to instantiate some constructor, only the author and the doc. You'll still be reading suggested method docs. It's just that your IDE .. as you say it, holds your hand.