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

@RobW: Thanks for the insight. 

I also think that such an app modernization process is the most reasonable way.

I never had a chance in my job as software developer and architect to rework the whole important apps just with some new technologies without additional business values. In my experiences such a project will fail, since at the end everyone will ask "So what's new? The UIs don't change at all?" and such an answer like "Oh we change the technologies under the hood, but the UIs look the same" won't help... OK, I never work for Google which has the power "money and resources" to re-write everything from scratch 😂

I also haven't seen that just because of using new technologies your apps could be extended easier than before.

One thing I always see as a good value is to take apart a huge app and build smaller deployable parts. 

I've written this article as an example: https://dzone.com/articles/enterprise-applications-customization-with-microse 

Cheers

Lofi

Jonathan Franchesco Torres Bca schrieb am Freitag, 22. Januar 2021 um 18:38:10 UTC+1:

Hi, Alexander.

I'm jofrantoba. I'd like working but my english is basic.

My best is the reading. 

atte @jofrantoba

https://youtube.com/playlist?list=PLAFyX6INxrfkdBLuF_oNlPlQj1nYhEYdg

GWT 2.7  RPC/RequestFactory

Google App Engine /Java

http://devolpay.com/#X

El dom, 20 dic 2020 a las 10:16, 'Alexander Bertram' via GWT Users (<google-we...@googlegroups.com>) escribió:

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.

https://jobs.bedatadriven.com/software-engineer

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-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/89d82553-ef82-4ead-a619-b3f125bd4036n%40googlegroups.com.