I'm assuming it is - in dev mode (hosted in their browser) it is supposedly debuggable as java byte code, which is interesting. In prod, I'm not so sure.
But yeah, I totally agree. It seems to integrate with third party JS, so the generated stuff can't be *that* hard to understand. The main downside is that it is java project only. On 22/06/2009, at 1:33 AM, Myles Byrne wrote: > On Mon, Jun 22, 2009 at 10:15 AM, Lincoln Stoll <[email protected]> > wrote: > > I guess less time in dev, consistency in testing and language for > development, potentially more efficient output, integration with > existing code? > > I'm not using it at the moment, but in some ways it looks interesting. > > Seems reasonable. As long the js is debuggable. Having to learn js > (and more importantly, the GWT style of 'compiled' js) because the > abstraction leaked would be my main concern as a java developer. You > can't use sass without already knowing css, but if you can write GWT > without knowing javascript then you may be running the risk of > digging a very deep hole. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
