JavaScript and Node.js news blog covering libraries, frameworks and tutorials, including the 'Let's Make a JavaScript Framework' series; it has since ended.
HN commenters recommend it for the sheer number of JS libraries and microframeworks it covers, praise its framework series, and suggest submitting projects there.
My path so far with javascript (with examples!):
Desire to make neat web pages. Learn enough jQuery so that you can make something move and change colors with maybe two lines of javascript instead of 20. Keep trying to one up yourself in what kinds of cool shit you can make (I use the term shit because you won't be making anything useful persay, but it will be something that will make friends say "Shit, that is cool. How did you do that?")
Start to learn more and more jQuery until you think in callbacks and events.
Use the canvas to make weird patterns (treeowls.com).
Make something using Ajax (try the hnsearch api: pretty fun http://zacharymaril.com/HNSearch/Topics/testing-api.html).
Try to solve a hard problem with JS that requires lots of computing (some work with Ramsey theory: http://zacharymaril.com/thoughts/constructionGraph.html) .
Mess around with Three.js (http://mrdoob.com/blog/post/693) and Processing (http://zacharymaril.com/).
Use chrome or firefox with the debugger.
Then get bored with frontend stuff and jump into node on heroku or whatever hosting service is popular but has good documentation. Make a chatroom with a lazy bot(zackbot.com) and a static file server. Look into the database bindings. Look at the stuff DailyJS puts out on node(http://dailyjs.com/tags.html#lmawa old with bugs, but very in depth for the time). Make something neat (still working on that part).
Read a bunch of Javascript/jQuery blogs. If you learn that way, pick up JS The Good…
I try to keep my subscription to an absolute minimum since I like to leave some time for reading books. After a lot of culling, I'm currently subscribed to some popular feeds:
http://www.smashingmagazine.com/ (general web design / dev)
http://www.alistapart.com/ (long form web design / front-end)
http://dailyjs.com/ (Javascript / node.js)
http://createdigitalmusic.com/ (digital music / software)
http://www.creativeapplications.net/ (new-media art)
And a handful of unpopular ones:
http://www.ribbonfarm.com/ (absolutely my favorite blog in the world – self-describes as "refactored perception)
http://www.tempobook.com/blog/ (same author as above, posts related to his last book)
http://worrydream.com/feed.xml (not really a blog, but Bret Victor writes some of the best long-form articles on interaction design around – read all of them)
http://www2.technologyreview.com/rss/video_rss.aspx (Tech Review videos, sparsely updated – mainly because the editor's interviews are awesome/hilarious)
http://idlewords.com/ (breathtaking travel blog from the founder of Pinboard)
http://www.loper-os.org/ (awesome / hilarious posts by a software heretic on the general terrible state of things in technology – keeps me in touch with Alan Kay-esque thinking)
http://we-make-money-not-art.com/ (the only contemporary art blog I like from a very dedicated Italian writer)
http://vagueterrain.net/ (occasionally published digital art magazine, themed topics, guest…
I think the recommendation to use request tokens still stands[1].
I haven't really had the chance to dive into html5/client-side js apps yet -- but it should be possible to apply the same idea to single-page apps as well? Perhaps even easier, as you don't need a fall back to plain http/1.1 on the client side, as you can already assume the client is able to run javascript, and you could do a lot of stuff to manipululate/validate tokens there.
Having a good implementation (not having to roll your own) would be good, though. Judging by [2] you might have to implement it yourself. Although [3] and [4] looks promising for express.js at least.
I have not had time to review this -- so preform your own due diligence.
[1] https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet#General_Recommendation:_Synchronizer_Token_Pattern
[2] http://stackoverflow.com/questions/6617499/for-node-js-is-there-a-csrf-token-module-that-works-with-ajax
[3] http://dailyjs.com/2012/09/13/express-3-csrf-tutorial/
[4] http://www.senchalabs.org/connect/csrf.html
reporting the links here in csv formats for easy processing -
Warning: the hn parser appends the quotes to the url when you click. sorry about this
"Collective by CoDrops","http://tympanus.net/codrops/collective/"
"CSS Weekly","http://css-weekly.com/"
"Web Design Weekly","http://web-design-weekly.com/"
"Responsive Design Weekly","http://responsivedesignweekly.com/"
"The Sass Way","http://thesassway.com/"
"Sass News","http://t.co/j0fMGWu9ng"
"Web Standards Library Update by Flippin’ Awesome","http://flippinawesome.org/category/news/best-of/"
"Best of JavaScript, HTML & CSS by Flippin’ Awesome","http://flippinawesome.org/category/news/best-of/"
"HTML5 Weekly","http://html5weekly.com/"
"JavaScript Weekly","http://javascriptweekly.com/"
"Node Weekly","http://nodeweekly.com/"
"Web Tools Weekly","http://webtoolsweekly.com/"
"DailyJS","http://dailyjs.com/"
"ng-newsletter","http://www.ng-newsletter.com/"
"Ember Weekly","http://emberweekly.com/"
"Today’s Readings by Aaron T. Grogg","http://aarontgrogg.com/blog/category/todays-readings/"
I posted this last week. Maybe it can help you.
http://news.ycombinator.com/item?id=2353962
- Join the jsmentor mailing list.
- Secret of a javascript ninja
- 10 things I learned from the jquery soruce [1]
- 11 More Things I Learned from the jQuery Source [2]
- Read the annotated version of underscore [3]
- write your own plugin. Follow this tutorial from Dailyjs[4]
- Launch emacs and write some code.
[1] http://paulirish.com/2010/10-things-i-learned-from-the-jquery-source
[2] http://paulirish.com/2011/11-more-things-i-learned-from-the-jquery-source
[3] http://documentcloud.github.com/underscore/docs/underscore.html
[4] http://dailyjs.com/tags.html#lmaf
Check out http://dailyjs.com/ some time. Granted, it's devoted to all things JS (not just frameworks), but the number of libraries and microframeworks and plugins for frameworks is absolutely astounding.
I don't remember ever seeing anything like this level of churn, and I've been programming since the early nineties. Not with Java, not with Python, not with anything.
Someone above mentioned rolling their own stuff with vanilla JS (which provoked an immediate invocation of Greenspun's tenth rule). My sense is that a lot of people start out this way and say, "Lo, a library! Github!"
One hopes that the cream rises to the top, but I'm drowning in milk.