OK, fair enough. I just wasn't sure if you had the Gadget problem space specifically in mind.
On Wed, Dec 15, 2010 at 10:10 AM, [email protected] <[email protected]> wrote: > Just in case it is not clear what I am trying to ask... > > The original question post began by (I thought) implying that this is > not a concrete example and is peppered with words and phrases like "if > every gadget", "potentially", "hyptothetically speaking" "in this > hyptothetical example" and "in this kind of case". What I'm asking is > - from the GWT team's POV, are there potentially classes of problems > for which the whole thing "cannot be compiled" (some kind of mashup of > disparate, but - for simplicity sake - somehow trustable code bases) > in which GWT would just have too little insight to the problem at > large to actually optimize - thereby effectively making it a non-ideal > choice... Or if the GWT team had such a problem at hand - would they > choose GWT, and if so, how would they deal with the implications > spelled out above? > > -- > 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. > > -- Eric Z. Ayers Google Web Toolkit, Atlanta, GA USA -- 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.
