Java 26 is here, and with it a solid foundation for the future

Re:Java 26 is here, and with it a solid foundation for the f... by chii on Tuesday March 17, 2026 @11:24PM (#47421301)

> You write your frontend in JS/TS, your backend in the same language, your build tools understand it natively, and you share types between client and server.

that's an excuse imho. It's a post-facto justifying using js on the serverside because of familiarity.

I know because the exact same reason was given for GWT (google web toolkit), and that failed pretty horribly (despite it being quite good imho).

[ Parent | on HN ]

Re:Java 26 is here, and with it a solid foundation for the f... by rossjudson on Tuesday March 17, 2026 @11:36PM (#47421362)

GWT was a huge success, and eventually became obsolete -- which is not the same as "failing horribly".

It took a long time for the web ecosystem to build up the capabilities that removed the need for GWT.

For a while, it was quite a good way to build and heavily optimize certain kinds of web client applications.

[ Parent | on HN ]

Re:Java 26 is here, and with it a solid foundation for the f... by gf000 on Wednesday March 18, 2026 @03:45AM (#47422780)

Yeah, I believe some ex-Googlers even claimed that writing Gmail was simply impossible at that time with ordinary JS, and the abstraction behind GWT was an absolute necessity (though maybe the frontend part was not all that important - closure compiler is still alive though)

[ Parent | on HN ]

Re:Java 26 is here, and with it a solid foundation for the f... by chii on Wednesday March 18, 2026 @08:39AM (#47425005)

On the other hand, gwt did not gain much traction, and the majority of frontend developers disliked it (granted, they do prefer javascript+css rather than coding the frontend via gwt widgets).

[ Parent | on HN ]