What's bad in Java
- From: Jack <jack@xxxxxxxxxxx>
- Date: Sat, 31 May 2008 21:46:17 +0200
.. Java programs are slower (Swing and JVM)
.. Swing layouts are not efficient to get desired result
.. There is a memory footprint overhead (compared to primitive sizes)
.. The GC freezes the application from time to time
.. It's impossible to add a method to a JDK class
.. The difference between checked and unchecked exception
.. Collections class are badly designed, they try to do too much
.. Starting thread is easy but synchronizing results in the GUI is harder
.. Having to code methods to access fields is dumb, it should be "transparent"
.. The JDK gives access to a ridiculously small part of an OS features
.. It's not possible to free memory when i'm sure i wont use it again
I hope the next release will address these concerns.
.
- Follow-Ups:
- Re: What's bad in Java
- From: Andrea Francia
- Re: What's bad in Java
- From: Lew
- Re: What's bad in Java
- From: Andrew Thompson
- Re: What's bad in Java
- Prev by Date: Re: three public domain java icons
- Next by Date: Re: Designing a Card Game
- Previous by thread: Concurrency and Performance
- Next by thread: Re: What's bad in Java
- Index(es):