Nothing here yet.
Nothing here yet.
No publications yet.
Shai Almog Yes, We have big plans for this, we love open source and we will keep providing open source version of our tools, we are currently working on website and actually going through the official DominoKit company registration, we plan to extend and expand our tools and the features they provide. Our goal is to be the #1 target for java developers in this area.
With the new GWT now mixing both echosystems -Java and JavaScript- have never been this easy, Now we can have the best of the two worlds without sacrificing anything, with how JsInterop has evolved and the elemental2 libraries and other alternatives that barrier has long gone. Now in GWT are talking the browser API we can mix html native elements with our own developed custom element seamlessly, we use the browser native APIs. We have tools that allows us to share lots of our code between backend and frontend, we have excellent type checking, we have strong contracts, and awesome IDEs. In DominoKit we took one step further and decided to build a full modern stack that cover most of the areas for building a modern web application : Domino-ui : https://github.com/DominoKit/domino-ui Very rich easy to use UI library with a good look and feel that uses html native elements and API. Domino-jackson : https://github.com/DominoKit/domino-jackson JSON (de)serializers for Java objects that uses jackson style and annotations, The same mapper works on the browser and the JVM, and support a very wide set of Java data types. Domino-rest : https://github.com/DominoKit/domino-rest Generate REST clients from jax-rs interfaces shared between frontend and backend. Domino-history : https://github.com/DominoKit/domino-history Manipulate the browser URL with an easy to use API and listen to the URL changes, routing have been this easy. Domino-aggregator : https://github.com/DominoKit/domino-aggregator Wait for different async tasks to complete before doing some action. Domino-slf4j-logger https://github.com/DominoKit/domino-slf4j-logger slf4j logging right in the browser. Domino-mvp : https://github.com/DominoKit/domino-mvp Light-weight but rich and comprehensive flexible MVP framework to control your application screens life-cycle And if this is not enough, the community has a lot more to add, even Java itself is getting better and we are keeping up. For the hiring part I think that is one point that need to solve, nowadays what we need is not a GWT expert, all you need is a java developer with little html and css knowledge, GWT is not just a compiler, just like TypeScript it is just the echo-system around it.
Thank you for this article, I am the author of @dominokit which domino-ui is part of, I am using GWT in a big project, 264+ screens, around 100K LoC, running in production in 14+ sites, The team started with 2 developer working on both frontend and backend, then reduced to 1 developer since it was enough to keep up with a 10+ backend developers adding features to the application. We have great look and feel UI, excellent performance, the is compiled and jzipped on the wire to just 800KB, and most important excellent maintainability, we can get any #java developer to ride in in few hours when we want. GWT have never been dead, we got version 2.9 recently with java 11 support, and 2.10 is coming very soon, and after that we are doing java 17 support and add language features. we already implemented some thanks to Colin Alworth. The community around GWT despite being small but it is a very active community, try to ask a question in the gitter channels or in the google group and see how fast you will get the answer. The tools and frameworks around it have also been under heavy active development, those are modern tools and frameworks that covers almost every aspect if web development, and you get it all with one stack, Java.
