4 ms·
A few major reasons: - The verbosity of Java wears on me very quickly. - I can't stand working in an IDE. - Documentation is abysmal. - I'm not familiar wit
by thenduks 16y ago
A few major reasons:
- The verbosity of Java wears on me very quickly.
- I can't stand working in an IDE.
- Documentation is abysmal.
- I'm not familiar with the ecosystem (so I don't know what to use and when -- What's 'Struts'? What's 'Tiles'?) and there doesn't seem to be a place to learn.
- vijaydev 16y agodisagree on the documentation point.
- thenduks 16y agoPerhaps not the documentation of Java itself, but practically every third-party library I've ever tried to use has been a disaster. At least with Ruby or Python I can just dig into the source code, but with so many FactoryFactory's around...
- vijaydev 16y agowell, I'll agree to that! Especially the factories :)
- idleworx 16y ago- I can't stand working in an IDE. Are you saying this because you mostly work with smaller web apps, or other reasons? For larger projects I find IDE's (especially Eclipse for JAVA indispensable).
- thenduks 16y agoI work mostly on large web apps but that doesn't have much to do with my dislike for IDE's. The reason I don't like them is that I don't want 90% of what it gives me. My 'IDE' is 1 gvim per project and a terminal app with a couple tabs. I can't think of anything an IDE gives me that I don't a) want or b) already have.
- democracy 16y agoThat is pure denial, not a very professional approach