News for hackers. Stuff that matters.
Re:String.intern() by QuercusMax on Monday May 15, 2017 @09:05PM (#14346626)
I think by "native" they mean "implemented-in-c++-by-the-JVM", which potentially vary; not java.util.HashTable, which should be pretty standard across JVM implementations.
Re:String.intern() by electrum on Tuesday May 16, 2017 @01:05AM (#14347488)
Yes, although Hashtable is legacy from JDK 1.0. New code should use HashMap or ConcurrentHashMap.
Re:String.intern() by Tharkun on Tuesday May 16, 2017 @02:20AM (#14347733)
Please be careful with blanket statements like this. HashMap, Hashtable and ConcurrentHashMap behave differently in certain (subtle?) ways. ConcurrentHashMap doesn't like NULL but is thread-safe. Hashtable is synchronized, slow and thread-safe, but doesn't mind NULL. HashMap is not thread safe and doesn't mind NULL.

Edit: pardon the dupes, on unreliable mobile link :-(

Re:String.intern() by josefx on Tuesday May 16, 2017 @09:04AM (#14349191)
> Hashtable is synchronized, slow and thread-safe, but doesn't mind NULL.

The issue with Hashtable or rather all legacy collection classes is that the API is rarely useful without additional synchronization. So you might as well use a HashMap wrapped by Collections.synchronizedMap or use a ConcurrentHashMap with a placeholder object instead of null.