blocks|key|230241|text|我认为这里要记住的关键一点是，Coffeescript就是javascript。每个Coffeescript语句或魔术操作符在Javascript中都有一个独特的具体表示。例如，Coffeescript中的(x)+->+x+*+x将直接转换为function+(x)+{+return+x+*+x;+}。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|230242|如果不知道Coffeescript将生成的Javascript，您就无法真正编写Coffeescript。首先，生成的Javascript是您需要调试的内容。如果有什么不同的话，我相信写Coffeescript可能会提高你对Javascript的理解，因为它迫使你做出Javascript独有的决定。例如，当在Coffeescript中，你决定使用=>而不是->，实际上你正在决定是否要绑定this+-这是一个非常真实的Javascript问题。|230243|何时(或是否)开始使用Coffeescript？我认为这个问题的答案或多或少取决于你。试一试，如果你觉得使用Coffeescript更容易完成任务，那就坚持使用它。如果您发现很难用与运行的语言不同的语言(因此也就是您必须调试的语言)编写代码，那么请返回到Javascript。|230244|entityMap^0|2V|C|3D|U|0|4U|2|4Z|2|5F|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|K|$]]

I think that the crucial thing to remember here is that Coffeescript IS javascript. Every Coffeescript statement or magic operator has a distinct concrete representation in Javascript. For instance <code>(x) -&gt; x * x</code> in Coffeescript will translate directly to <code>function (x) { return x * x; }</code>.

You can't really write Coffeescript without being aware of the Javascript it will generate. For one thing, the generated Javascript is what you will have to debug. If anything, I believe that writing Coffeescript could possibly improve your understanding of Javascript, because it forces you to make decisions that are unique to Javascript. For instance, when in Coffeescript, you decide to use <code>=&gt;</code> instead of <code>-&gt;</code> in reality you are making a decision about whether or not you want to bind <code>this</code> - a very real Javascript problem.

When (or if) to start using Coffeescript? I think the answer to this is more or less up to you. Try it out, and if you feel that it is easier to get your tasks done using Coffeescript, then stick to it. If you find it difficult to write the code in a different language from the one that runs (and thus the one you have to debug), then go back to Javascript.

blocks|key|231187|text|我想谈谈你的顾虑。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|231188|1)如果你已经使用JS三年了，你可能对JS有一个相当扎实的理解。如果你还没有完全理解，也许是时候用一本好的JS书来补充你的知识了。|231189|2)+Coffee-script可能不会让你的JS知识变得更差。设计Coffee-script应用程序的方式与设计JS应用程序的方式相同(在大多数情况下)，因此您获得的设计技能将会传授给您。在我看来，程序设计是编程中最重要的方面。|231190|3)为什么不信任JS？为什么你信任你使用的任何其他编译器/解释器/其他工具？我怀疑Coffee-script是没有bug的，但许多人将它用于许多目的。这意味着已经测试了大量的行为，通常是在生产环境中，所以您的用例可能已经尝试和测试过了。|231191|4)当然，由Coffee-script生成的JS对您来说是陌生的，因为生成它的规则并不优先考虑人类的可读性。然而，阅读它会增加您对JS的了解，因为您会看到编写的程序是如何运行的。这就把我们带回到了第一点。|231192|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I'd like to address your concerns. 

1) If you've been using JS for three years, you probably have a pretty solid understanding of JS. If you haven't gained a solid understanding yet, it may be time to supplement your knowledge with one of the good JS books. 

2) Coffee-script probably wont make your knowledge of JS worse. The way you design Coffee-script applications is the same way that you would design a JS application (for the most part), so the design skills you gain will transfer over. Program design, in my opinion, is the most important aspect of programming.

3) Why don't you trust the JS? Why do you trust any of the other compilers/interpreters/other tools you use? I doubt Coffee-script is bug free, but many people use it for many purposes. This means that a large set of behavior has been tested, often in production, so your use case has probably already been tried and tested. 

4) Of course the JS generated by Coffee-script will look foreign to you, since the rules for generating it don't have human readability as a priority. Reading it, however, will increase your knowledge of JS as you see how peculiarly written programs run. This brings us back to point 1.

blocks|key|2888511|text|下面是我对这个话题的看法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2888512|2888513|JS不是一种支持技术(支持什么？)。它是一种主要在前端使用的语言，在后端使用它有一种新的趋势。由于浏览器本身并不支持CoffeeScript，除非您将其用作后端，因此我认为使用CoffeeScript没有意义。尽管学习一门新语言总是一个好主意，但|ordered-list-item|2888514|并非如此。实际上，使用CoffeeScript就像使用不同的语言。学习其中一个并不能让你在另一个中变得更傻。除非你停止学习另一个。|2888515|，没有证据表明CoffeeScript会编译成有错误或速度慢的代码。实际上我使用CoffeeScript已经有一段时间了，我没有观察到有任何性能影响，|offset|length|style|BOLD|2888516|实际上你不需要理解为什么会这样编译。如果您在后端使用CoffeeScript，那么您甚至不必查看它编译成的代码(您只需要源代码)。至于使用它来编写浏览器脚本，是的，使用它可能有点困难(调试)。这就是为什么我总是建议为浏览器编写普通的JavaScript，并在后端使用CoffeeScript。|2888517|2888518|现在谈到最后一个问题:我认为CoffeeScript根本没有影响我的JS知识。我将它们视为独立的语言。此外，除非您想在前端使用CoffeeScript，否则不需要了解JS就可以切换到CoffeeScript+(尽管您应该这样做)。|2888519|无论如何，掌握JavaScript也是的一个好主意。:)|2888520|entityMap^0|0|0|0|0|1V|3|0|9|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|10|8|@$J|11|K|12|L|M]]|9|@]|A|$]]|$1|N|3|O|5|E|7|13|8|@$J|14|K|15|L|M]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|V|$]]

So here's what I think about the topic:

<ol>
<li>JS is not a supportive technology (support for what?). It is a language mostly used on front-end and there is a new trend of using it on back-end. Since browser do not support CoffeeScript natively than unless you use it as a back-end then I don't think there is a point in using CoffeeScript. Although learning new language is always a good idea.</li>
<li>Not at all. Actually using CoffeeScript is like using different language. Learning one cannot make you dumber in the other. Unless you stop learning the other one.</li>
<li>There is no evidence that CoffeeScript compiles to buggy or slow code. Actually I am using CoffeeScript for some time and I didn't observe any performance hit.</li>
<li>Actually you don't need to understand why it compiles like this. If you are using CoffeeScript on back-end then you don't even have to look at the code it compiles into (you only need the source code). As for using it to make browser scripts then yes - it may be a bit difficult to work with it (debug). That's why I always advice to write normal JavaScript for browsers and use CoffeeScript on back-end.</li>
</ol>

Now as for the last question: I don't think that CoffeeScript affected my JS knowledge at all. I treat them as separate languages. Also you don't need to know JS in order to switch to CoffeeScript (although you should) unless you want to use CoffeeScript on front-end.

Also mastering JavaScript is always a good idea, no matter what. :)

blocks|key|232613|text|你应该理解Coffeescript应该解决的问题。为此，您应该对javascripts的“坏部分”有一个基本的了解。我建议读一读Douglas+Crawford关于这一点(有一本书，但也有很多互联网资源。只需搜索"javascript错误部分“)。基本上，这个想法是“在所有那些笨拙的大括号和分号之下，JavaScript的核心总是有一个华丽的对象模型。CoffeeScript试图以一种简单的方式公开JavaScript的优点。”(摘自coffeescript的网站)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|232614|有一个叫做jslint的工具可以帮助程序员避免javascript陷阱。这个工具会分析你的代码，并给出常见错误的警告，比如全局变量、分号插入、名称空间污染等。|232615|Coffeescript转换为javascript。但是它生成的javascript是一个标准子集，与jslint高度兼容。更重要的是，它生成在所有浏览器上都有效的javascript代码。因此，它不仅仅是一个很好的语法糖层，它确实有助于生成可靠的代码。|232616|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

You should understand what problems Coffeescript is supposed to solve.
And for that, you should have a basic knowledge of javascripts' "bad parts".
I suggest reading Douglas Crawford about that (there's a book, but also a lot of resorces on internet. Just google "javascript bad parts").
Basically, the idea is that "Underneath all those awkward braces and semicolons, JavaScript has always had a gorgeous object model at its heart. CoffeeScript is an attempt to expose the good parts of JavaScript in a simple way." (taken from coffeescript's site).

There's a tool to assist programmers to avoid javascript pitfalls called jslint.
This tool analizes your code and gives warnings about common mistakes, such as global variables, semicolon insertions, namespace pollution, etc...

Coffeescript translates to javascript. But the javascript it generates is a cannocical subset, highly compliant with jslint.
What's more, it generates javascript code valid on all browsers.
So it is not just a nice syntactic sugar layer, it really helps generate solid code.

So basically I have a number of concerns holding me back from coffeescript:

<ol>
<li>I'm not really an expert in js yet, even though I'm using it for around 3 years now I still feel like I'm missing something important about it. Since it's mostly a supportive technology for me I never find time to go in depths of js ( which, I admit, might be a wrong attitude ).</li>
<li>My js knowledge will get even worse if I'll start Using coffeescript</li>
<li>I'm not sure if I can actually trust coffescript, meaning the js code it compiles to</li>
<li>At times I don't understand the js code coffeescript compiles to and even worse - why it compiles like that.</li>
</ol>

I'd like to know your thoughts on the above points. The crucial one is:
How using coffeescript affected your knowledge of js? And how important you think it is to fully understand js before switching to coffeescript?

the right time to use coffeescript

编译器

解释器

因此，基本上我有一些顾虑阻碍了我对coffeescript的使用：我还不是一个真正的js专家，尽管我已经用了大约3年了，但我仍然觉得我错过了一些重要的东西。因为它对我来说主要是一种支持性的技术，所以我从来没有时间深入研究js (我承认，这可能是一种错误的态度)。如果我开始使用coffeescriptI'm，我的js知识...

问使用coffeescript的合适时机
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用coffeescript的合适时机EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用coffeescript的合适时机
EN