TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The Story of Google's Closure: Advanced JavaScript Tools

36 点作者 mariorz超过 15 年前

4 条评论

andrewljohnson超过 15 年前
What he doesn't tell you is how much the Reader code would be if it was just gzipped. That's the real comparison to make.<p>If gzipping alone would get the code down to 800kb or something, then the improvement made by closure doesn't seem so awesome.<p>Nonetheless, it's obviously good to get the file size down to the absolute minimum when you are going to serve millions or billions of copies.
评论 #930479 未加载
评论 #930495 未加载
barrkel超过 15 年前
I find this whole Closure story amusing, because what it amounts to is applying static typing techniques to a dynamic language - and guess what, static typing makes "it easier to catch errors much earlier". Where are the dynamic typing extremists when you need them?
评论 #930815 未加载
neilc超过 15 年前
<i>Mihai estimates that without Closure, Reader's JavaScript code would be a massive 2 megabytes</i><p>Wow. That just seems wrong to me.
评论 #930526 未加载
cloudhead超过 15 年前
I'd be interested to know how it compares to the current version of Dojo.