Brian is great in its own way and doesn't need to be compare to Pike at all. And he has to admit lot of problems as Java is doing things quite opposite of what was done decade or so back. Go leads are not doing this because Go is not changing course when they do they may admit more.
Valhalla and Loom example you gave shows how important lightweight concurrency and memory layout of object is. Go had this from day 1. For faster release after Go 1.1 /1.2 they always had 6 month release schedule which Java implemented few years back. While Java is running impressive projects for last 10 years to add these features.
Before Go came along Java never really published or committed to performance numbers for GC. It was always Here are few GCs, use whatever works for you. Now they give far more details after Go pushed for numbers.
> Barring a change in leadership, generics is almost certainly the last new language feature
Pike is already retired many years back, he is not in any official position in Go project.
For sure, you like Java and I am working fine in Java like forever. But you seem to be losing all sense of perspective here.
Valhalla and Loom example you gave shows how important lightweight concurrency and memory layout of object is. Go had this from day 1. For faster release after Go 1.1 /1.2 they always had 6 month release schedule which Java implemented few years back. While Java is running impressive projects for last 10 years to add these features.
Before Go came along Java never really published or committed to performance numbers for GC. It was always Here are few GCs, use whatever works for you. Now they give far more details after Go pushed for numbers.
> Barring a change in leadership, generics is almost certainly the last new language feature
Pike is already retired many years back, he is not in any official position in Go project.
For sure, you like Java and I am working fine in Java like forever. But you seem to be losing all sense of perspective here.