Repository files navigation CoffeeScript and Unit Testing
web/native development
slow standard evolution [get numbers]
runs everywhere (*)
functional paradigms
mature library support
verbose/inconsistant
bad parts to avoid
just JavaScript
[get some history]
popular/supported [get stats]
Dropbox
Kickstarted compiler framework
Node.js
CoffeeScript
jQuery/underscore/Backbone
PhantomJS
Bootstrap
CoffeeScript in 10 minutes
JSON/objects
functions
@/this
Framework (Yeoman, etc) vs diy
Cakefiles - classic build environment with separate source, output
Server-side
declarative syntax - less comments, still clear
Great simplified versions of common JS patterns
Class definitions
Functions are free
Rewarded for making nice code
More complicated environment
Write/debug different languages
Need to know JS pretty well (especially @)
long-term maintainability - dev tools don't offer much support
Everything else is the same (JS vs CS)
JS OO limitations
difficult to find mature libraries - cobble them together or swallow the pill
browser incompatibilities
performance/experience not as good as native apps
Essential for maintainable dynamic code
pay back some of the time savings
tdd to the point practical
works for well-defined requirements
more difficult for exploratory code
don't be lazy and never get back to it
simple - test one thing, minimize dependencies
assume nothing for expectations
need to watch it fail
external dependencies
async code
setup/teardown
sinon for server response
waitsfor/runs
ensure path is followed
About
CoffeeScript talk for FCIP
Resources
Stars
Watchers
Forks
You can’t perform that action at this time.