GWT is the very good framework which gives you flexibility to use their in-built widgets or functionality as well allow to work on low level API or customize framework to your need like compiler linker etc. My company does 100% in GWT and Java. Using only one standard language for both server and client that works on all browsers is brilliant and unique.
-Nagin kothari www.zilicus.com On Mon, Apr 16, 2012 at 1:57 AM, Erron <[email protected]> wrote: > +1 GWT is too complicated. I think even for experts in GWT and/or Java you > would have to admit that GWT is quite verbose which turns off alot of JS > developers. From what I have seen, Dart looks to be the evolution of GWT. > But it still has a longs way to go to be as mature as GWT. > > > On Sunday, April 15, 2012 5:03:07 AM UTC-4, Joshua Kappon wrote: >> >> I personally believe that someone at Google decided GWT is too >> complicated for web developers out there and has failed the test of getting >> traction (I know a lot of people are using it, but I think they were aiming >> for a number similar to the JS community). >> I personally think that Dart is out there only as an attempt to pull more >> Java Scripters in, because they feel GWT failed to do that. >> Dart runs natively on chrome, but also compiles to JS (just like GWT) - >> so it can support all modern browsers. >> >> I started this thread because I feel there are a lot of GWT developers >> who really want to hear Google's thoughts about GWT in the future. I also >> feel that in this last year, people are discovering it and thinking about >> adopting more than before, but they are driven away by Google's official >> silence (Personally, I know of 3 companies who decided it is a risk, and >> chose BackBone.JS instead) >> >> Don't get me wrong, I am thankful to the contributors community, but I >> think Google should say something as Google about this. >> >> >> >> >> On Sunday, April 15, 2012 11:39:47 AM UTC+3, dominikz wrote: >>> >>> I actually think that the whole mess with Dart is actually to develop a >>> single platform for both Google products: Android and Chrome. >>> >>> Imagine that in a couple of years you could write in the same language >>> both native (to Android) and browser applications. Wouldn't it make be >>> great? Of course from Google perspective, if they are only thinking about >>> promoting their own products (Android), because they surely don't care >>> about Windows Phone or iPhone. >>> >>> In my opinion they are going a way to encourage to use their products >>> and discourage to use other's. Imagine you have (through Dart) a very easy >>> way of developing native application, or close to native with a web >>> language (Dart). Of course those would only have 'native' L&F for Android >>> and Chrome. For all the other browsers they will put some sort of >>> 'compatibility layer' (javascript) that will not have all those cool >>> features (animations, etc.). >>> If the developers catch this idea, people will tend to use Chrome and >>> Android more, because of a better experience. >>> >>> What do you think about that theory? >>> >> -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/9jcRLdMkjmkJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- Nagin Kothari Co-founder, Zilicus Solutions www.zilicus.com -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
