> 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.
Both statements here are untrue. GWT is not a 'fat client' at all - it requires no plugin and is compiled to Javascript before deployment (runs like any other Javascript in your browser). Vaadin is an extension to GWT that is also compiled to Javascript and runs client-side. You must be getting your 'wires crossed' and mistaking GWT/Vaadin with some other technology.
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.
Here in London, UK, I doubt that you would get planning permission for a home built wind turbine. I love the idea of local power generation and DIY but even I have to admit that few people have the skills to ensure bits of this don't fly off in high winds.
Any body know why I need the qttask.exe running all the time? Ive turned off the taskbar function and sadly every time I view a QT video it puts its RunOnce entry back in the registery.
Ive seen a TV clip of a wheel chair performing the same trick.
The demo showed a large adult sitting in the chair which was balancing on two wheels. The guy was thrown a weight that made the chair wobble but it easily recovered. This was all on a hard smooth studio floor but still pretty impressive.
They didnt say if this was anywhere near production.
Slashdot Mirror
Dam yanks ;)
> 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.
Both statements here are untrue. GWT is not a 'fat client' at all - it requires no plugin and is compiled to Javascript before deployment (runs like any other Javascript in your browser). Vaadin is an extension to GWT that is also compiled to Javascript and runs client-side. You must be getting your 'wires crossed' and mistaking GWT/Vaadin with some other technology.
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 ;)
Here in London, UK, I doubt that you would get planning
permission for a home built wind turbine. I love the
idea of local power generation and DIY but even I have
to admit that few people have the skills to ensure bits
of this don't fly off in high winds.
... 2 was hand on bosom outside shirt
..but you can still buy VHS gear from them. Cheap way to get lots of publicity.
> 1) Since Nokia owns 48% of it,[cut]
> 4) The reason Symbian exists, is that Nokia doesn't wan't to spend resources to development of an OS.
Bit of a contradiction here? Nokia is using
a resource the size of 48% of Symbian on OS
development.
What about Nokia?
I know M$ is bad and GNU/Linux good beyond that I get a cluster headache.
My major complaint against BT is the one
year rolling contract:
http://www.bt.com/terms/pdfs/bt1050.pdf
I know a couple of people who have been stung
by this.
Given that they have a monopoly on DSL and
cable broadband sucks it would be foolish to
go into dispute with them.
This seems like a good thing to me. One of the advantages of Linux not been driven by a need to produce revenue.
Any body know why I need the qttask.exe
running all the time? Ive turned off the taskbar
function and sadly every time I view a QT video
it puts its RunOnce entry back in the registery.
Here is a link:
n ew chair.htm
http://www.dynopower.freeserve.co.uk/homepages/
Ive seen a TV clip of a wheel chair
performing the same trick.
The demo showed a large adult sitting
in the chair which was balancing on
two wheels. The guy was thrown a weight
that made the chair wobble but it easily
recovered. This was all on a hard smooth
studio floor but still pretty impressive.
They didnt say if this was anywhere near
production.
So when can we have power over bluetooth? ;)