Ahoj, my jsme narazili na dva zasadni problemy: a) vygenerovany JS nejde v podstate profilovat/debuggovat b) pro vetsi aplikace roste doba kompilace a spotreba pameti behem kompilace - pro 300 000 radek kodu pocitej s desitkama minut a 12 GB pameti
A pak obcas neco prestane fungovat, treba split pointy, takze misto vice mensich JS souboru compilator generuje jeden obrovskej. A najit proc si mysli, ze je nejakej kod dosazitelnej znamena debuggovat dovnitr kompilatoru. Lukas On Mon, Sep 26, 2011 at 10:33 AM, x y <[email protected]> wrote: > Chcem sa spytat na skusenosti s GWT na projektoch(Vyhody/nevyhody). Ci ma v > dnesnej dobe zmysel postavit projekt na tejto technologii, ak ma tak v akych > pripadoch ju zvolit/nezvolit. > > Podla http://www.thoughtworks.com/radar zjavne GWT nieje dobrou volbou. > Citujem: > GWT is a reasonable implementation of a poor > architectural choice. GWT attempts to hide many of > the details of the web as a platform by creating desktop > metaphors in Java and generating JavaScript code to > implement them. First, in many ways, JavaScript is > more powerful and expressive than Java, so we > suspect that the generation is going in the wrong > direction. Secondly, it is impossible to hide a complex > abstraction difference like that from event-driven > desktop to stateless-web without leaky abstraction > headaches eventually popping up. Third, it suffers from > the same shortcomings of many elaborate frameworks, > where building simple, aligned applications is quick and > easy, building more sophisticated but not supported > functionality is possible but difficult, and building > the level of sophistication required by any non-trivial > application becomes either impossible or so difficult > it isn’t reasonable. > >
