3 ms·

But almost everything in Java is more verbose, and so you'd end up writing "preprocessors" for everything (and the strong, static, explicit typing means that a

by apu 17y ago

But almost everything in Java is more verbose, and so you'd end up writing "preprocessors" for everything (and the strong, static, explicit typing means that a lot of this preprocessing would have to be rewritten for even slightly different cases). So why not just cut-out the middle man and work in a higher level language directly?

axod 17y ago
>> "But almost everything in Java is more verbose" Sure, that's the common misconception. You're correct. However, if you actually look at the language and write stuff in it, you'll find it's not actually true. The issue is when people look at some existing insane Java code and cite it as proof Java is verbose. I'd absolutely agree - most open source / freely available Java code is verbose. Several of the libraries (enterprise etc) are verbose and insane. But that's not Java. Higher level languages are not always better. Use what is suited to the job at hand. I'm far more comfortable working at lower level than high level. Which is better.... talking high level and relying on a compiler/runtime to figure out what you want? or just talking a bit lower level in the first place.