Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

- I'll try to make an example of simple MicroUI, actually I already plan this and the project is already there on Github ;-) https://github.com/gwtboot/microfrontends-example - Debugging: It is as fast as debugging JS webapp. You just debug on browser, see:

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

and have other reasons 1. debugging speed reason 2. Is it possible to hire someone who is willing to use GWT? lofid...@gmail.com 于2021年3月4日周四 下午6:46写道： > ... and in the beginning everything is small and fast but you'll see the > same problem (also with pure JS or any other technologies) if you

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

agree. Cheers. lofid...@gmail.com 于2021年3月4日周四 下午6:46写道： > ... and in the beginning everything is small and fast but you'll see the > same problem (also with pure JS or any other technologies) if you build one > huge app... > > This is similar to the backend problem... Monolith vs. Microservice

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

In fact, We just did it like you're saying, every project composes with a different maven module. But , one difference is , the final output material is one xxx.nocache.js . the sense may cause build speed too slowly. Could you describe " separate the project (Maven, etc) in smaller projects and

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

... and in the beginning everything is small and fast but you'll see the same problem (also with pure JS or any other technologies) if you build one huge app... This is similar to the backend problem... Monolith vs. Microservice --> Monolith UI vs. Micro UI... lofid...@gmail.com schrieb am

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Thanks for the information! Why don't you just separate the project (Maven, etc) in smaller projects and integrate them just in the HTML files DOM / ScriptInjector? So in general you could build many Micro UIs (many JS files) in GWT and integrate them in one HTML DOM or put them together

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

In the past years, My company build a larget HIS frontend platform based GWT , The large means: lot of module, code by java , output to javascript seems beautify But, when the application more bigger, the compiler package speed more slower; debug, publish will wait long time... Recently, we

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

> Sharing POJO definitions between client and server is the biggest advantage of GWT for me along with static typing in the frontend. Can't live without these two. Not needing POJOs in a dynamically typed language (JS), could be considered an advantage, due to less code needing to be written.

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

A few years ago, a client of mine was thinking about switchung to Vue. So, I startet learning Vue. To do so, I search the internet, bought a book, install npm, code the examples and so on ... Two or three weeks later, my virus scanner (oh yes, I am a Mac user that has a virus scannner ... my

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Hm the thread was about why not using java for frontend development but now has general tips for GWT. The padlet is cool. Thanks for assembling it. My 2c. I have used GWT RPC in the past but I was not happy with it. The main reason was that I couldn't decouple server and client from GWT

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Some tips I could say: - GWT is a transpiler / compiler to JavaScript, *so the result only runs on Web browser, no server component*. Server container or Web server only used for delivering the HTML, JS and CSS. So actually you could just use the result JS from the file system and

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

We also have a Padlet for GWT  I try to collect all the information about GWT / J2CL on one Black Board: https://padlet.com/lofidewanto/gwtintro There are articles, presentations, groups and other information for a modern GWT / J2CL development... Hope this helps! mysare...@gmail.com

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Thank you very much. I ll give it a try. On Friday, December 18, 2020 at 4:44:32 PM UTC+1 frank.h...@web.de wrote: > > Lofi has some interesting things to look at: > * GWT Awesome Library List (Gwit a LiLi) > * there is also a boot starter for gwt, but I do not recall the name. > > Good

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Lofi has some interesting things to look at: * GWT Awesome Library List (Gwit a LiLi) * there is also a boot starter for gwt, but I do not recall the name. Good starting points are: * gwt-maven-archetypes: https://github.com/tbroyer/gwt-maven-archetypes *

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

I am new here, so hello everyone. I am very interested in this topic. I have gotten tired of the whole javascript ecosystem. I did not know that you could easily have GWT run only on the frontend and used jee/spring/whatever on the backend as you please. I always thought it was a client-server

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

On Mon, Oct 19, 2020 at 1:56 AM lofid...@gmail.com wrote: > Thanks Craig for the info... > > I'm not familiar with React (only Hello World ) > > Can you integrate React with these GWT React frameworks? So write your > components in Java and integrate them back into React JavaScript? > >-

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Thanks Craig for the info... I'm not familiar with React (only Hello World ) Can you integrate React with these GWT React frameworks? So write your components in Java and integrate them back into React JavaScript? - https://github.com/GWTReact/gwt-react -

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

> Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser? Because of React. Companies are investing in creating reusable React components. Reacts virtual DOM makes it very difficult to integrate a React component into a GWT app, so you end up just using React, and

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Also agree with general opinions in this thread: - Actually it is enough to know Java and its ecosystem. - The APIs of those UI frameworks + Web browser as a platform (Web APIs) have to be learned by all Java or JavaScript or TypeScript developers anyway. - As I saw it by myself,

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

I am in the same situation, But this is wrong. and it is not that hard to make any java developer work on GWT especially if they claim to know some frontend since that implies that they know HTML,CSS, JS which is more important than knowing GWT. On Tuesday, October 6, 2020 at 3:47:35 PM UTC+3

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

I am still don't know why people call the developer like this, GWT developers, Angular developers, React developers...etc.. have we ever called developers like `Spring developers`, `hibernate developers`, `Rest developers` ..etc... I would say we have Java developers and JS developers,

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Hi Lofi, In my company we are the only group that is working with GWT to develop a new customer facing application. We have a few products in maintenance mode that are also using GWT. But most new developments are using Angular. The biggest problems we are facing with using GWT/Java for the

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

One thing to the Mocking framework: https://mswjs.io it looks indeed very interesting. In GWT I used to implement the mock implementation in "development time" and remove it in "production time" by using GWT options for different "sourcepath" and "entry point" with help of DI. It works very

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Hi Thomas, thanks for the feedback. This is my point of view as a Java developer I did some Polyglot projects and have written my summary here from 2011: - English: http://lofidewanto.blogspot.com/2011/10/why-is-polyglot-programming-or-do-it.html

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

I can't choose which security scanner to use. That's already defined by clients. Maven is not an option. Regards, Rodolfo On Tue, Sep 29, 2020 at 11:03 AM lofid...@gmail.com wrote: > Hi Rodolfo, > > thanks for the insight. > > Yes, I think SonarCube is standard tool for the quality of the

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

On Tuesday, September 29, 2020 at 12:08:36 AM UTC+2, lofid...@gmail.com wrote: > > OK, now I understand you  > > Yes, we always have to separate the Client and the Server part. This is > also GWT best practice. > > But if you are using JavaScript on browser you lose the advantages like: > >

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Sorry Lofi, I misunderstood you. Fully agree with you! Il giorno martedì 29 settembre 2020 alle 10:56:26 UTC+2 lofid...@gmail.com ha scritto: > Ahh, I mean not only "Maven" just a *build tool* like Maven, Gradle, > Buildr, Bazel, Ivy or whatever...  > > The main thing we need to *manage the

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Sorry Lofi, Il giorno mar 29 set 2020 alle ore 10:57 lofid...@gmail.com < lofidewa...@gmail.com> ha scritto: > Ahh, I mean not only "Maven" just a *build tool* like Maven, Gradle, > Buildr, Bazel, Ivy or whatever...  > > The main thing we need to *manage the dependencies and versions*. > >

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

> If Maven or some other tool decides to update one of the selected jars > used by my project, it can introduce a version marked as a high security > risk. That's something I can't allow. > You define a specific library version in your dependency management tool. There are also tools for

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Hi, I don't want a tool to manage dependencies for me because that means I may lose clients concerned with security. I wrote a web app used by a couple of large banks. Each new release must pass extensive security tests before deploying. Code must be reviewed using SonarQube, dependencies must

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Hello Lofi, Some loose comments: - Another great advantage I enjoy is that I don't need Maven. Can you rewrite your example _without_ depending on Maven? And without using a library that relies on annotations? - VisualStudio code is great for Java and JavaScript. You can also use Eclipse with

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

OK, now I understand you  Yes, we always have to separate the Client and the Server part. This is also GWT best practice. But if you are using JavaScript on browser you lose the advantages like: 1. We use *Java* as the language 2. We have the best *ecosystem* like libraries, frameworks,

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

If the server part is a Java servlet that handles REST calls, there is no need for GWT at all. No need to deal with JSInterop and no need to deal with annotations, that's cleaner code! If you have a server that exposes a REST API, you can write the client in anything. JavaScript is great in the

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

I'm not sure whether I follow you... what is the difference using Java / GWT + REST and TypeScript + REST... The server part is the same. The web browser part is also the same. The difference is only the language and ecosystem you use on the web browser... Thanks, Lofi rmr...@gmail.com

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Hi Lofi, I once used GWT + Electron + Materialize running with Jetty. That worked, but after getting rid of GWT the code was much cleaner. Class com.sun.net.httpserver.HttpServer is more than enough for running a Java server with REST interface on the desktop. Another advantage of moving away

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Hi stockiNail, first of all thanks a lot for the feedback... *1 and 2. JsInterop: *yes the mapping Java / JS is not trivial, you need to know both worlds. Therefore I think the idea like DefinitelyTyped is not bad. They put everything for

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

Hello Lofi, Java + GWT + GXT + Eclipse was my main toolkit for over a decade. When Sencha went crazy with the price of license renewals, I started looking for alternatives. Today my toolkit has changed to Java for backend/server side, TypeScript for client side and Visual Studio Code for code

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

First of all, let me say I'm a Java developer and I'm using GWT since years. Having started developing java since 1996 (with java 1.0.2), I have seen many technologies and frameworks to help a java developer can use to build a UI on web browser (like applets, servlets, jsp, jsf, webstart). I