4 ms·

I've never done front end before (I just hate the JS syntax, so I've avoided it, besides a few jsonp requests) but with CoffeeScript I was persuaded to give it

I've never done front end before (I just hate the JS syntax, so I've avoided it, besides a few jsonp requests) but with CoffeeScript I was persuaded to give it a try. Here is my problem. Nothing is Google-able. Even basic things that I get caught up on the answer on IRC is usually "look up how to do it in JS, and then reform it to CS". Maybe I'm starting on the wrong stuff, but even though the syntax is wonderful, actually using libraries is a pain. I'm only on my 2nd day though, so maybe this is just the normal language growing pains.

bruth 15y ago
http://jashkenas.github.com/coffee-script/ http://jashkenas.github.com/coffee-script/ http://coffeescriptcookbook.com/ http://coffeescriptcookbook.com/ Tutorial/screencast links: http://stackoverflow.com/questions/5124706/is-there-a-screencast-tutorial-site-for-coffeescript http://stackoverflow.com/questions/5124706/is-there-a-screen... A talk by Jeremy: http://ontwik.com/javascript/jeremy-ashkenas-on-coffeescript/ http://ontwik.com/javascript/jeremy-ashkenas-on-coffeescript...
- 3pt14159 15y ago
  Interesting. I'd gone through the first link before, but the second is quite good. Still doesn't change the fact that most libs you are using are written in JS (not to mention a whole new platform, the browser) and therefore harder to Google for, but thanks for your help.
dualogy 15y ago
2 days? Give it 2 weeks and you won't look back. I do think it's more suitable to writing a "new big app from scratch" -- fixing up some consulting client's website with some new JS widget and 5-20 lines of integration scripting or some such isn't the use-case where CoffeeScript gives you a notable advantage.
bruth 15y ago
> "actually using libraries is a pain" Maybe that is your source of confusion.. when you write CS code, you can use any existing JS library. The syntax is just different for what you write.
ricardobeat 15y ago
You should really learn Javascript first. Coffeescript is not (yet) a replacement for it, more like a tool.

bruth 15y ago

http://jashkenas.github.com/coffee-script/ http://jashkenas.github.com/coffee-script/ http://coffeescriptcookbook.com/ http://coffeescriptcookbook.com/ Tutorial/screencast links: http://stackoverflow.com/questions/5124706/is-there-a-screencast-tutorial-site-for-coffeescript http://stackoverflow.com/questions/5124706/is-there-a-screen... A talk by Jeremy: http://ontwik.com/javascript/jeremy-ashkenas-on-coffeescript/ http://ontwik.com/javascript/jeremy-ashkenas-on-coffeescript...

3pt14159 15y ago
Interesting. I'd gone through the first link before, but the second is quite good. Still doesn't change the fact that most libs you are using are written in JS (not to mention a whole new platform, the browser) and therefore harder to Google for, but thanks for your help.

dualogy 15y ago

2 days? Give it 2 weeks and you won't look back. I do think it's more suitable to writing a "new big app from scratch" -- fixing up some consulting client's website with some new JS widget and 5-20 lines of integration scripting or some such isn't the use-case where CoffeeScript gives you a notable advantage.

bruth 15y ago

> "actually using libraries is a pain" Maybe that is your source of confusion.. when you write CS code, you can use any existing JS library. The syntax is just different for what you write.

ricardobeat 15y ago

You should really learn Javascript first. Coffeescript is not (yet) a replacement for it, more like a tool.