Friday, January 22, 2021

Re: Our 10+ year journey with GWT (+ job opening)

Similar decision process for us. After a lot of research into Vue, React etc we decided the switch over and learning curve just didn't pay back. Our app scaffold in GWT is actually really solid, and it's easier for us to add more modern approaches like a JSON based REST API and newer layouts and widgets (like Material Design) into that framework rather than throw it all away. A big benefit is we can do it step by step, panel by panel too if we want - making it much more manageable to refresh the overall app.
On Friday, 22 January 2021 at 06:53:34 UTC Marco Castillo wrote:
It is nice to hear all this experience with GWT. I would like to share mine. I'm based in Guatemala, our development team develop a product, Axeso, it is a product that enhances the security in Google Apps (next GSuite, now Google Workspace). We develop the administrator console using GWT, the backend in Google App Engine using java mainly and NoSQL databases, and at this time (almost ten years later) we're deciding what new framework would be the successor of GWT.
I was considering https://gwtmaterialdesign.github.io/gwt-material-demo/, we would like to give our console a more material design look. And with all the stories I just read, maybe I will ditch React (it was going to be our choosed framework for substituting GWT) and kept GWT.
Regards


Marco
On Wednesday, January 20, 2021 at 10:14:32 AM UTC-6 David Nouls wrote:
That is actually a good point indeed. We also have very old tech in production including some ALGOL.

I do have the impression that the JS Frameworks race has been slowing down a bit. Sure there will always be some new ideas, but the big frameworks are there for quite some.

At least with GWT/Java it is rather easy to maintain! GWT does not change much, sometimes that is an advantage.
On 20 Jan 2021, 16:48 +0100, lofid...@gmail.com <lofid...@gmail.com>, wrote:
IMHO that's the problem with frameworks / languages. If they are "strong enough" they won't be gone... I don't think that TypeScript / Vue.js / React / Angular etc. will be vanished. They will stay forever just like COBOL and other technologies like Borland / Embarcadero Delphi Object Pascal. My comment above was a joke, because I don't know what will happen in 10 years. There will be another hot things. Maybe we move completely on the native client development instead of Web browser? But who knows...

So at the end of the day the devs need to maintain apps with the zoo of frameworks and languages. 

Scary if you see this history of web frameworks: https://raw.githubusercontent.com/mraible/history-of-web-frameworks-timeline/master/history-of-web-frameworks-timeline.png

I think, it's time that the development of apps / Web apps should go higher in the abstraction level to be technology / framework independent. PIM (Platform Independent Model) anyone?  😉

BTW.: I still have JSPs in production. Also COBOL 😅

Cheers,
Lofi
t.br...@gmail.com schrieb am Mittwoch, 20. Januar 2021 um 14:36:30 UTC+1:
Why did you bet on GWT 10 years ago and wouldn't bet on TypeScript nowadays?
(fwiw, TypeScript is already 8 years old; Vue.js is 6 years old, React is 7)

On Tuesday, January 19, 2021 at 5:26:38 PM UTC+1 lofid...@gmail.com wrote:
@swas...

<quote>
Yes, almost 10 years for me too and production application  running for 3 years.
GWT 2.6.1 + Eclipse 4.8.  Tomcat8 + MySQL5.7  + Java8 + JasperReport
my next 10 years plan is  move to TypeScript + VueJS.
</quote>

After 10 years, will we still be able to see TypeScript + VueJS? 😂

Cheers,
Lofi
RobW schrieb am Dienstag, 19. Januar 2021 um 15:29:42 UTC+1:
Our web front end is on 15 years with GWT as of this year, and we're expecting 5 more with luck. So we'll hit the 20 year mark if all goes well

On Tuesday, 19 January 2021 at 10:46:44 UTC aka...@gmail.com wrote:
I wonder if that will actually last for the next 10 years.

On Tuesday, January 19, 2021 at 10:04:19 AM UTC+2 swas...@gmail.com wrote:
Yes, almost 10 years for me too and production application  running for 3 years.
GWT 2.6.1 + Eclipse 4.8.  Tomcat8 + MySQL5.7  + Java8 + JasperReport
my next 10 years plan is  move to TypeScript + VueJS.
On Monday, 4 January 2021 at 23:37:53 UTC+7 Alexander Bertram wrote:
Nice to hear from everyone!

Here's to the next ten years :-)

Best wishes for 2021,
Alex

On Tuesday, December 22, 2020 at 10:22:08 AM UTC+1 Segun Razaq Sobulo wrote:

I've been using GWT for 7+ years (with appengine java backends) and actively looking for a job. I'll push my resume.

Thanks
On Monday, 21 December 2020 at 15:24:19 UTC+1 aka...@gmail.com wrote:
We are in times where working remotly id actually a good option.

On Monday, December 21, 2020 at 4:19:13 PM UTC+2 David Nouls wrote:
Hi Alex,

Same story here. I have been working with GWT since it first came out. For our current project we again opted for GWT because we share a lot of code between client and server and productivity is high.

I'm not available at the moment (maybe end of next year)… but living in Belgium/Leuven I don't think that is doable. Relocation is not an option. Good luck finding people, there are not a lot on the market.

Groeten,
David
On 20 Dec 2020, 16:16 +0100, 'Alexander Bertram' via GWT Users <google-we...@googlegroups.com>, wrote:

Dear all, 

I hope this email isn't too off-topic, but I wanted to share an opening for a job on our team with a large GWT component.


The first version of our product, ActivityInfo, a data collection and analysis platform for humanitarian relief, was built with GWT, GXT and Google Gears in 2009 and seriously would not have been possible without GWT. 

In 2018, nearly 10 years later, we looked at the amazing js ecosystem and considered moving to Typescript or Elm.

Instead, we decided to keep the bits that we loved about GWT: the typesafety, code-reuse with the server, i18n, code splitting, linkers, and the amazing compiler, and add SCSS for styles and our own port of Preact + rxJava-like reactivity for dom manipulation using Elemental2.

Three years after the start of ActivityInfo 4.0 we couldn't be happier with the choice, and are more productive than ever. 

If you're an experienced GWT developer that would enjoy the challenge of a working on a modern GWT codebase, I hope you'll consider joining our team!


Best,
Alex

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/46240bd9-f716-4448-a481-acfc87229f8fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6f3ebf9a-df0e-464c-b88b-c57f539fc030n%40googlegroups.com.

No comments:

Post a Comment