H
Heinz Kabutz
javaspecialists.eu · Personal blog · on HN since 2009
Heinz Kabutz writes the Java Specialists' Newsletter, with articles on Java internals, concurrency, collections, and language changes.
What HN saysHN commenters recommend it for its long archive of Java articles and cite its issues in debates over Java coding practices.
17HN people shared it
6linked it in comments
16stories submitted
132story points
2 years agolast shared
2009people per year2026
Most-shared posts
- 1Issue1873 people · first shared 2011
- 2Homepage2 people · first shared 2011
- 3Java 7 changed the structure of String1 people · 101 points · first shared 2015 · 86 comments on HN
- 4Escape Analysis in Java explained1 people · 8 points · first shared 2009 · 1 comments on HN
- 5Collections.checkedCollection()1 people · 3 points · first shared 2017 · discussion on HN
- 6Book Review: Good Math1 people · 3 points · first shared 2014 · discussion on HN
- 7Virtual Thread Deadlocks1 people · 2 points · first shared 2022 · discussion on HN
- 8Please Don't Yield a Lot1 people · 2 points · first shared 2024 · discussion on HN
- 9How consistent is weakly-consistent iteration?1 people · 2 points · first shared 2021 · discussion on HN
- 10JavaSpecialists 300: Break in Switch with Pattern Matching1 people · 2 points · first shared 2022 · discussion on HN
- 11Delaying Garbage Collection Costs1 people · 2 points · first shared 2011 · discussion on HN
- 12Thread Confinement1 people · 1 points · first shared 2014 · discussion on HN
- 13Gazillion Virtual Threads1 people · 1 points · first shared 2022 · discussion on HN
- 14Garbage Collection and P99 Latency1 people · 1 points · first shared 2023 · discussion on HN
- 15Sorting Lists1 people · 1 points · first shared 2016 · discussion on HN
What HN people wrote when they linked it
AKluge · 2017-05-16
Some good content along the same vein with 16 years worth of articles: http://www.javaspecialists.eu/
ggeorgovassilis · 2011-04-18
Java specialist newsletter. Discusses design patterns and advanced topics.
http://www.javaspecialists.eu/
IBM's developer works. Focused on libraries and frameworks used in the enterprise and new technologies.
http://www.ibm.com/developerworks/
alex3305 · 2023-08-25
> I cringe every single time I see a for loop for what System.arraycopy () has been providing since early days.
The worst thing is, that System.arraycopy() is an optimized JNI call which is much faster than copying it by hand [1].
> For better or worse, it shows me that the author isn't that into Java.
The thing is though, most of the time arrays in Java are used because of performance. Or maybe ignorance. Because why would anyone voluntarily give up all the comforts of a List<T>? It's not that Collections are very hard to find in the documentation. And most of the IntelliJ suggest switching to a Collection anyway.
1. https://www.javaspecialists.eu/archive/Issue124-Copying-Arrays-Fast.ht…
pauldbourke · 2013-03-05
I was going to do a post rebuking the points made, but rather unsurprisingly it seems plenty of others already have done so, in a manner much less arrogant than OP's.
http://www.javaspecialists.eu/archive/Issue187.html and http://onjava.com/pub/a/onjava/2003/11/19/exceptions.html?page=2 are two well written sources of many that Google turned up on the subject.
mcherm · 2013-03-05
I would encourage you to do that post. Because the two documents you linked to are very unconvincing when placed beside David MacIver's essay.
The first link (http://www.javaspecialists.eu/archive/Issue187.html) says the code was hard to understand, that this is the 'wrong' way to use exceptions, that reusing a normal exception type instead of an exception intended for control-flow might mask other exceptions, and that debuggers will pause. These are MacIver's points #4, #2, #6, and #5 and he debunked each one.
The second link (http://onjava.com/pub/a/onjava/2003/11/19/exceptions.html?page=2) says "This not only makes the code difficult to read, but also makes it slower." That is MacIver's points #4 and #1 and he debunked them.
Do you feel that any of MacIver's points are incorrect? Do you know of any arguments that he did not already address?
Uchikoma · 2011-09-07
Although exceptions have become faster, and you can speed them up (overwrite stack generation code), they are slow mostly due to filling the stack trace. Mostly based on this:
http://www.javaspecialists.eu/archive/Issue187.html