3 ms·
I didn't like python at first. The mentality of "hardware is cheap, there's no need to be that fast" drove me away from it full speed. However, I was short on t
by bayindirh 8y ago
I didn't like python at first. The mentality of "hardware is cheap, there's no need to be that fast" drove me away from it full speed. However, I was short on time for something, and I gave it a try, then I actually liked it a lot. It's very practical and fast enough for most cases.
The string processing capabilities has blown me away, however it didn't change my love for higher performance, compiled languages. Now I use it for small system tools or prototyping, but for highest performance I still use C++.
Similarly, I disliked Java. It felt slow, heavy, bloated, unnecessarily Enterprise. Again, using it changed most of the perception. I found out that for some stuff it's pretty competent, it's easy to write sophisticated stuff. GUI classes and event based XML parsers are very well thought out. I also found out that Java's infamy came from bad programming, especially in the GUI part. JDK tends to correct your GUI programming errors to simplify the stuff, however this "auto-mending" came with a performance penalty which adds up with every small mistake you make. So you need to write your code carefully. Frameworks like JaDE made me like Java even more.
In the end, most of the like/dislike comes from preconceptions and prejudice if you ask me. If the language you're using is up to the task you have at hand, and you understand the trade-offs you make with a language, there's no need and reason to dislike a language.
- tpxl 8y agoTBH Java used to be a lot worse than it is now :)
- bayindirh 8y agoI've first used Java in the early 2000s. I think I've seen some of these times. It was fun nevertheless. :)
- Sohcahtoa82 8y ago> It felt slow, heavy, bloated, unnecessarily Enterprise. You can avoid the "unnecessarily Enterprise" by not writing code in the Enterprise fashion. Not every class needs to be an extension of an abstract class that implements an interface. Not every class needs a factory class. Not every operation needs to be abstracted. If you have a class that has just a constructor and a single function, you probably don't need a class and can just write a function. Most complaints about Java are really complaints about some idiotic Java paradigms that seem to have been invented by someone that measures productivity in LoC written or classes implemented.
- bayindirh 8y agoJava's "unnecessarily enterprise" feeling didn't come from the paradigms that increase the LoC (abstraction, interfaces, factory classes, etc.), but from the way it developed, where it used and how it behaved. This feeling is also reinforced by the prime editors of that time: Eclipse and Netbeans. Both are behemoths which were written in Java, heavy, resource intensive and somewhat slow. In the 2000s, Java wasn't that fast and refined, and it showed and felt profoundly, at least by me. With the open sourcing of Java and the performance jump happened with Intel's Core i series CPUs, Java got a lot lighter. I've never had hard feelings against any programming language, and I hold no grudge against Java, but I currently don't need it, so I'm not using it.