GWT 2.0
code.google.com
GWT 2.0
1–10 of 34 posts
Re: GWT 2.0
#2Great Toolkit if you want to/can utilise the Java Tools echo system and everything else that comes with it and with the newer version the UIBinder allows for declarative UI. I personally haven't used the Code Splitting feature but i can see its uses.
A common misconception is that it doesn't allow writing direct JavaScript - it actually does.
Re: GWT 2.0
#3What I think Google should do is build a Silverlight competitor that is open source.
What's the point of this Javascript hacking with suboptimal results?
Re: GWT 2.0
#4What I think Google should do is build a Silverlight competitor that is open source. What's the point of this Javascript hacking with suboptimal results?
> What's the point of this Javascript hacking with suboptimal results?
Javascript performance has been making huge leaps in the past few years, and Google is helping to drive that further. Plus, penetration is hard. Javascript availability is practically 100% vs. Silverlight's 20%.
Re: GWT 2.0
#5What I think Google should do is build a Silverlight competitor that is open source. What's the point of this Javascript hacking with suboptimal results?
> What's the point of this Javascript hacking with suboptimal results? Javascript performance has been making huge leaps in the past few years, and Google is helping to drive that further. Plus, penetration is hard. Javascript availability is practically 100% vs. Silverlight's 20%.
It's not just about speed. But even if you focus on speed, Silverlight will always be much faster.
Check out this c64 emulator in Silverlight 3:
http://channel9.msdn.com/posts/Dan/Honorable-Mention-MIX09-S...
Re: GWT 2.0
#6What I think Google should do is build a Silverlight competitor that is open source. What's the point of this Javascript hacking with suboptimal results?
I think Google is actually thinking javascript is going to be the base machine language of the browser. They seem to be investing a lot of effort on the V8 engine. http://code.google.com/p/v8/
Re: GWT 2.0
#7What I think Google should do is build a Silverlight competitor that is open source. What's the point of this Javascript hacking with suboptimal results?
I think Google is actually thinking javascript is going to be the base machine language of the browser. They seem to be investing a lot of effort on the V8 engine. http://code.google.com/p/v8/
Why would Google think such a thing when Silverlight has better tech? Why not build a Silverlight competitor?
Re: GWT 2.0
#8Great Toolkit if you want to/can utilise the Java Tools echo system and everything else that comes with it and with the newer version the UIBinder allows for declarative UI. I personally haven't used the Code Splitting feature but i can see its uses. A common misconception is that it doesn't allow writing direct JavaScript - it actually does.
Yes I have used it a fair bit to write javascript - in some ways it provides the boring bits of stuff around js (like module-like systems, name spaces etc..).
If you like IDEs, IDEA from jetbrains even knows when you are doing inlined JS and assists you as you code.
I thought I would hate GWT by now, but its one of those things that mostly stays out of my way. Would I used it for a new project from scratch? Not sure... maybe. There are lots of other options now for more classic web approaches that dont' require it to be a monolithic ajax app (and jquery is pretty hardened to provide a lot of the glue/lubricant).
Re: GWT 2.0
#9Great Toolkit if you want to/can utilise the Java Tools echo system and everything else that comes with it and with the newer version the UIBinder allows for declarative UI. I personally haven't used the Code Splitting feature but i can see its uses. A common misconception is that it doesn't allow writing direct JavaScript - it actually does.
> Java Tools echo system
Took me a while to figure out what the heck this "echo" is.
Re: GWT 2.0
#10What I think Google should do is build a Silverlight competitor that is open source. What's the point of this Javascript hacking with suboptimal results?
It's called Webkit. And GWT uses it.