> Even Orkut closing the doors, it doesn't mean their code is going away > anytime soon :)
You're killing me, Goktug. The backwards compatibility knife had already pierced my heart, and this just shimmied it around a bit. :-) I had to refresh on memory on PotentialElement, but it looks virtual DOM-ish; making fake elements that are really pure JS objects, and then later converting them into real DOM objects only as-needed. I believe it sped up the first page load of Orkut by ...15%? or so. I also vaguely recall that, AFAIU, the pipe dream was to have the entire initial DOM render be one huge .innerHTML=<blah>, since IE really liked that. But making strings that big hurts the GC such that (AFAIK) it's a wash in modern browsers to just making DOM elements directly anyway. Speaking of PotentialElement, looking at commits from around that time frame, there is also a change from Ray Ryan that turned useLazyWidgetBuilders = true, with a commit message of "in prep for deleting the old code". Looks like that deleting never happened...can we do that now? As with PotentialElement, I don't think useLazyWidgetBuilders had any external design docs, discussion, etc., so I don't really know the whole story on it. Or even little bits, other than I enjoy deleting old code and will volunteer to do that if we can. - Stephen -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/20140706220525.6ccc4472%40sh9. For more options, visit https://groups.google.com/d/optout.
