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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Sam Ruby, Brendan Eich, and Jeremy Ashkenas on CoffeeScript and "JS-next"

65 点作者 sstephenson超过 14 年前

6 条评论

gfodor超过 14 年前
The bottom line is while all the debate about how to improve Javascript is going on, all the while with no real changes coming to all browsers (I'm looking at you, IE), Jeremy went ahead and shipped something that's great that you can use now. As usual, the people who ship will win. Good luck with all the wrangling of the big vendors to change a tiny bit of syntax, I'll be happily sitting here writing CoffeeScript <i>today</i>.<p>All that's missing is a layer of tooling in modern browsers (Chrome, FF) that make it so you can look at CoffeeScript as if it were in the browser, and the abstraction would be pretty complete. You'll still have to precompile the stuff on your server, which sucks, but practically speaking we're not talking about anything that can't be clean and easy to use without appropriate tools. Generally speaking client side code is short and sweet, so running your system in development mode where the script compiles on the client and doing a full compile server side for production mode isn't that far off from doing a debug vs release build in the world of native apps.
评论 #1997881 未加载
olavk超过 14 年前
I'm not sure I believe in a new "built from scratch" standard language for the web. Sure, we could get rid of all the JavaScript cruft and mistakes, but wont we just replace them with fresh cruft and mistakes in the new language?<p>I believe in evolving the core JavaScript to be more flexible, and then innovate at a level above JavaScript, like CoffeeScript (or my own <a href="http://mascaraengine.com" rel="nofollow">http://mascaraengine.com</a>).<p>ECMA should not so much focus on building more powerful abstractions (like classes, packages) into the core language, but rather on making the core more flexible. E.g. adding continuations (if possible) would be much more valuable than adding classes, because classes can already be emulated at a higher level.<p>Stronger support in browsers for debugging would help everyone.
评论 #1997389 未加载
评论 #1997373 未加载
jashkenas超过 14 年前
The original blog post that kicked off the conversation is here: <a href="http://brendaneich.com/2010/11/paren-free/" rel="nofollow">http://brendaneich.com/2010/11/paren-free/</a><p>Some previous discussion and counterpoints here: <a href="http://www.reddit.com/r/programming/comments/eb3xt/so_you_kids_want_coffeescript_do_you_brendan_eich/" rel="nofollow">http://www.reddit.com/r/programming/comments/eb3xt/so_you_ki...</a>
olavk超过 14 年前
The idea about supporting source coordinate mapping in Firefox/Firebug is great! This could make it much more pleasant to debug generated JavaScript.
petercooper超过 14 年前
<i>So your “do both” suggestion is good, if it is possible: evolve JS while tracking up-and-coming languages, and try to align JS as it evolves with the best-of.</i><p>C# seems to have pulled this off over the years. It keeps taking ideas from other languages (I'm mostly aware of the Ruby ones) and leaping forwards. It's just a shame there's a stigma attached to it.
评论 #1998061 未加载
po超过 14 年前
<i>"Let a thousand little languages bloom, before picking your bouquet."</i><p>That's a fantastic way of approaching web standardization.