Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Handling JSON as a basics for language? Really? null restricted type will come with valhalla, string templates had a try, but people complained and they withdrawn them after 2 preview iterations. Not sure what issue people had with them and what issues maintainers noticed.

What do you mean by broken exception system?

Java is not a small language that you can throw features around, they have to take into consideration final goal of it and decades of development.



> Handling JSON as a basics for language?

Yes, even Mark Reinhold admitted that in the last "Ask the Architects" interview.

>null restricted type will come with valhalla

Will they? It's been 10+ years of Valhalla. Why is a compiler construct even behind project Valhalla? Kotlin has showed you don't need it to do them.

> string templates had a try

Yes they were over engineered and they failed to deliver a basic feature.

> Java is not a small language that you can throw features around, they have to take into consideration final goal of it and decades of development.

Yes I agree, but it shouldn't take YEARS to ship anything. 11 years for a JSON api?! Come on.


> Yes I agree, but it shouldn't take YEARS to ship anything. 11 years for a JSON api?! Come on.

Anything? Or maybe something that you specifically want?

It added records when I wanted them, it added streams and lambdas. I don't care for string templates (I thing those are ugly in any language).

null-restricted types would be nice but you have to understand that designing a language is not throwing every possible feature on top of it (like kotlin and resulting lack of readability it has and hard time updating to newer JDK), you have to design it, think of the possibilities, what users really want etc.

Valhalla type system results in addition of null-restricted types, as a natural evolution of the language.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: