Let me give another vote of confidence for CoffeeScript.
As a seasoned Javascript developer, it took me about four hours to become
comfortable with CS. It is a very small barrier, but the advantage is that
it makes doing the right thing in JS easy. functions are automatically
wrapped, variables aren't accidentally global, and the boilerplate in JS
mostly goes away, allowing the logic to shine through.
var x = (function() {
... code ...
})();
anyone?
Even if you choose to release the project in JS ultimately, it may be
worthwhile to write the first version in CS and compile to JS before you
release. While there are some peculiarities that show up in CS-compiled
code, (like returning every last instruction), these are easily cleaned up,
and the code will be cleaner in the end.
On Sunday, July 22, 2012 3:42:12 PM UTC+3, Alan Hoffmeister wrote:
>
> You guys are just killing me, I was planning to write with coffee script,
> but pure JS seems to be a better idea, I was planning async on the
> templates, but async is evil in there, now I was suggested to don't use
> MongoDB, and guess what db I was planning to use? hahaha
>
> @mlegenhausen, what was your trouble with NoSQL?
>
> This is a real awesome discussion, I could really process a lot of useful
> information, thanks for everyone that can/could spend their 1 cent here
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
