Hi, have you got references for your last paragraph?

It might have been fading but Ukraine has had a very tough past with Russia https://en.wikipedia.org/wiki/Holodomor , https://en.wikipedia.org/wiki/Orange_Revolution (the list goes on) doesn't recent history suggest a widespread resistance to the influence of Russia?

Have you got references for "proud of a history of embracing nazism" beyond a tiny minority that seem to be in many countries?

Have you got references for "culture erased by ukrainian ultranationalism"?

We hosted two Ukrainian women each with a child for two years after the Russian army started marching towards their homes. They were busy living their lives. One of the mothers hometown was https://en.wikipedia.org/wiki/Battle_of_Bucha#Mass_killings_in_Bucha

Do you have some metrics for "very badly divided country"? How does it compare to the UK after Brexit or the USA after the latest election?

Sorry, not a very coherent response. The harm done to real people by brazen lies pushed by Russia is truly insane.

I'm genuinely interested where you get your information and truly want an open an honest discussion.

Dam yanks ;)

Well going by http://en.wikipedia.org/wiki/Fat_client I think GWT fits this. It can run without a server at all...

Vaadin is much more than an extension to GWT. Vaadin uses GWT to implement the client side but like Wicket the client component tree is modelled on the server. Vaadin even uses the name Terminal in it's implementation https://vaadin.com/api/com/vaadin/terminal/package-summary.html

I've worked with GWT, Wicket a lot and recently done a comparison between Vaadin and GWT so maybe my wording is a bit odd but I think it accurately represents the three different approaches.

I'd definitely recommend GWT. Best bet for RIA with component based framework and taking advantage of Java and Java tooling. Also a really well thought out component library.

Be careful of Wicket/Vaadin. While GWT is a traditional fat client architecture (like Flash etc) Wicket/Vaadin are more like a terminal service with the client being executed on the server. i.e. user clicks/drags etc generally need to go to the server. So I'd stick to fat client (GWT, Flex...) or thin client like Spring MVC etc...

Isn't this exactly why the phrase "technical debt" makes sense? Google has decided to get into technical debt so they can get to market early. They then will presumably re-pay this debt as soon as possible. They just don't want people basing work off this short term nasty stuff.

I imagine we have all worked at places that are always racking up technical debt but I'm not sure this is true of Google.

I worked with Alan a long time ago. Never quite understood how he could cope with a shimmering wallpaper.

Anyway, the biggest compliment I've ever had was when he said my code was "fixable".

Sadly at the time I didn't know him from a bar of soap. Only that he locked out all out customers fixing an intentional spelling mistake in my code ;)