I can sympathise with some of what Bob is saying.
>From what I can gather there is actually a great flux of activity going on
behind the scenes by parts of the community. The main players in moving
GWT forward appear to be half-a-dozen or so companies who use GWT greatly,
and some
>
> With GWT getting old, this is becoming painful, because GWT did cool
> things, like animation and date pickers and rich text editors, by brute
> force back when that was necessary. Now, however, HTML5 and other things
> have evolved to offer better, cleaner solutions, but often it's
Ideally, twice yearly release of "stable", with most recent appropriate
patches applied, such as "2.201904" and "2.201910" or similar tagged
releases would definitely help there.
On 5/30/19 3:33 PM, Bob Lacatena wrote:
I just posted this elsewhere, but as this thread has more current
I just posted this elsewhere, but as this thread has more current
responses, I'm reposing it in the hopes that someone will read it:
GWT is suffering from a very serious publicity debacle. I'm actively doing
GWT development, and regretting every moment of it right now. Years ago I
loved
GWT is suffering from a very serious publicity debacle. I'm actively doing
GWT development, and regretting every moment of it right now. Years ago I
loved GWT. Today, I'm dreading it.
My biggest problem for the past year has been the fact that unless one
hunts for threads like this, GWT
