 |
Misconceptions
People's first impressions stick around a long time, even when false or no longer true. There are many misconceptions about Java. Largely because Java has evolved so quickly and people don't have time to reevaluate their opinions about each technology each time an update to that technology has been made. Hopefully this will be become a definitive list of misconceptions and their corrections.
- AlwaysUseStringBufferMisconception
- Clarification on when exactly to manually use StringBuffers for String concatenation.
- AssertionsAreFreeMisconception
- A pedantic discussion on the performance of assertions.
- ImmutableObjectsAreBadForPerformanceMisconception?
- A discussion on when immutable objects are actually bad for performance and how they can be used to improve performance.
- MicroBenchmarksAreMeaningfulMisconception?
- A discussion on why micro benchmarks? usually are not meaningful for anything useful.
- SynchronizationIsSlowMisconception
- An in depth discussion on when Synchronization is slow but more importantly when it is not slow.
- ForcingGCCuresOutOfMemoryErrorMisconception?
- Why trying to force GarbageCollection will not have any effect on OutOfMemoryErrors.
Discussion about Misconceptions
|