“Think! Think! Think!”, said Pooh.
I think it’s important to change perspective for a moment, from the Google PR and developer world perspective, to the competitive SEO perspective. I’m not saying any of this is true fact; I’m merely implying intent the same way Googlers often imply intent when looking at webmaster activity. I’ve seen Google employees look at a web site that appeared to be clean, and mark it untrustworthy simply because the webmaster appeared to associated with other sites that were not as clean. That’s the world Google forces us to live in, so Google should live in the same world. If Google expects us to be slimy, it’s a pretty safe bet that Google behaves that way as well.
Again… I’m not saying this is Google’s intent with Google Closure. I am saying that if I were Google, I would certainly explore this as an opportunity to advance my control the web without stifling innovation as much as I would otherwise have to… such as Google has been doing lately.
Related questions that Google should probably answer if it wants support from developers:
- is this intended to compete with jQuery? Compliment? Or are devs expcted to pack jQuery through Closure, too?
- why built another js minifier? Dean Edward’s Packer works very well… even better than Closure according to early reports.
- what about Google Web Toolkit js library? What’s the roadmap here.. or is there a js roadmap at all?