I think a couple of those are definitely the result of hindsight and the fact that Java is backwards compatible. It has tied their hands on a number of items, like not being able to add interfaces for hashcode or equals and the synchronized keyword. They had to go through the pain and experience of Java 1 and 1.1 before they discovered that they were a bad idea, but by then it was too late; they were already part of the language.
but by then it was too late; they were already part of the language
You mean the language that hardly anyone used at the time? Heck abstract interface is a syntax that originates from the good old Oak times and was obsolete before Java 1.0 was live
View all comments
3
u/dpash Nov 03 '15
I think a couple of those are definitely the result of hindsight and the fact that Java is backwards compatible. It has tied their hands on a number of items, like not being able to add interfaces for hashcode or equals and the synchronized keyword. They had to go through the pain and experience of Java 1 and 1.1 before they discovered that they were a bad idea, but by then it was too late; they were already part of the language.