Java 8: New features in ConcurrentHashMap

Re:Java 8: New features in ConcurrentHashMap by sdfsdufihwfuhdf on Wednesday January 18, 2017 @09:59AM (#13426710)

I tend to group languages into machine-code, VM, and interpreted. This tend to lead to similar tradeoffs within the group...with the exceptions of Golang.

in my mind: interpreted = why would you ever use a language like this? VM = fast, safe, but going to use a lot of memory machine code = fastest, low level HW access, usually unsafe

[ Parent | on HN ]

Re:Java 8: New features in ConcurrentHashMap by Tuna-Fish on Wednesday January 18, 2017 @10:06AM (#13426773)

Also Swift and Objective-C. For some reason people think they are fast because they are compiled. Yes, they are fast so long as you only write C in them. Actually using their features is typically way slower than Java.

[ Parent | on HN ]

Re:Java 8: New features in ConcurrentHashMap by hota_mazi on Wednesday January 18, 2017 @01:22PM (#13428769)

> I tend to group languages into machine-code, VM, and interpreted.

This distinction doesn't make much sense in 2017: most languages are blends of all these things with technologies like VM's, JIT, Ahead-of-time compilation, etc...

[ Parent | on HN ]

Re:Java 8: New features in ConcurrentHashMap by sdfsdufihwfuhdf on Wednesday January 18, 2017 @02:40PM (#13429610)

Underneath they're still divisible. AoT is always native machine code. JIT/VM/Bytecode is VM, basically machine code on demand.

Then there's interpreted code which has worked the same way for forever

[ Parent | on HN ]