DailyJS

This is what I came to suggest as well. I would also say that Express is a good one as well if you're looking to learn Node. Not quite as clear as the annotated source for Backbone, but well commented. I also liked the "Let's Make a Framework" posts at DailyJS. DailyJS in general was a great blog that is now closed, but the archives are still up. https://github.com/strongloop/express http://dailyjs.com/framework-index/

This is what I use. Daily: https://github.com/trending http://www.rssheap.com/articles Once a week http://css-weekly.com/ -- Mondays (sometimes Tuesday) http://html5weekly.com/ -- Wednesdays http://javascriptweekly.com/ -- Fridays Intro to follow certain leaders and such: http://uptodate.frontendrescue.org/ Javascript Specific: http://dailyjs.com/ CSS Specific: https://css-tricks.com/ Occasionally browse the "Picks" for Codepen: http://codepen.io/ Which is how I find awesome up-and-comers like mo.js http://codepen.io/sol0mka/full/ogOYJj/

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.

I've come to accept that HN is the place I go to satisfy my "intellectual curiosity" and more focused lists are where I go to get my learn on. For example, for JavaScript stuff: * http://reddit.com/r/javascript (yeah it's on reddit, but it's a great resource) * http://javascriptweekly.com/ ( https://twitter.com/JavaScriptDaily ) * http://coding.smashingmagazine.com/tag/javascript/ * http://dailyjs.com/ * http://javascriptshow.com/ (been a while since the last episode) * http://javascriptjabber.com/ (I haven't listened to any episodes yet, but I plan on it soon)

i've had good success with submitting some of my github'd js projects to http://dailyjs.com, decent amount of exposure there. make sure you have at least a demo/example page up somewhere, too.

Yes, we used it for http://www.akshell.com. Here's a blog post about the experience (in Russian but Google Translate should do a good job): http://habrahabr.ru/post/114749/. I started translating it to English for http://dailyjs.com but never had the time to finish it. If this comment gets enough votes I'll do it ;)

FuelUX has already received coverage at http://dailyjs.com/ :-D

http://dailyjs.com/ and http://microjs.com/ have been pretty useful for me.

So, the code you post requires jQuery, I am assuming, because you don't say. Which means you would need to also include jQuery in the header. Doesn't that seem like a waste? Also if you had jQuery already you could probably writing a queuing system for almost all actions, and not just "important" ones. You should take a queue from Flickr. I took a look at how they handled this, and I think it's one the best I have seen so far. http://dailyjs.com/2011/11/28/flickr-async/ The method there could actually be a small amount of code, and wouldn't require that you load jQuery before queuing events.

Yeah, that's good, as is: http://dailyjs.com/ Back in the day, Ajaxian was the necessary read, but no longer...

DailyJS has an excellent tutorial about using Express.js and Jade http://dailyjs.com/tags.html#lmawa

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 have http://dailyjs.com/ in my newsfeed.

Are you sure the thread pool isn't used for IO? I thought that was it's primary use. This explanation is a bit old but I think still correct: http://stackoverflow.com/a/20346545 and http://dailyjs.com/post/libuv

I'm waiting for vim in the browser... oh wait... http://dailyjs.com/2013/12/13/vimjs/ Still - I'll take it all back when someone shows me Wordstar.js. Who needs Indesign??

Survey summary has actual data without author's personal opinions mixed in: http://dailyjs.com/files/2013-survey-summary.pdf

Yes there is! http://dailyjs.com/2012/10/29/fuel-ux Glad to help if more questions come up

There are alternatives that don't require extending the language or having to work directly with a mess of nested callbacks. A bunch of flow-control libraries here: http://dailyjs.com/2012/02/20/new-flow-control-libraries/ This is definitely more hairy to use than if the language supported it natively, but not so bad, and can be implemented in a very lightweight way (this approach http://daemon.co.za/2012/04/simple-async-with-only-underscore/ is a few lines of code on top of Underscore.js which a lot of sites are using already). (PS: sorry if OP's article already mentioned this stuff, I can't load it at the moment)

Maybe have a look at Backbone.js: Hacker’s Guide: http://dailyjs.com/2012/08/16/mvstar-6/

dailyjs did a nice writeup recently http://dailyjs.com/2012/01/19/semicolons/ and isaac (npm guy) wrote a really good piece on it that I like better then mislavs http://blog.izs.me/post/2353458699/an-open-letter-to-javascript-leader… I don't even have a problem with people who want to put semi-colons all over the place, I am just tired of having to defend myself on why I choose not to. And it feels kind of odd that I have to, because I am not the one adding redundant characters everywhere

I hope not. Edit: I don't know of too many prominent JavaScript programmers who prefer not to use semicolons. http://dailyjs.com/2012/01/12/style/

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-sou… [3] http://documentcloud.github.com/underscore/docs/underscore.html [4] http://dailyjs.com/tags.html#lmaf

For the learning part: VM booklet in progress https://github.com/visionmedia/masteringnode Dailyjs.com series http://dailyjs.com/2011/01/03/node-tutorial-8/

Part 2 of the interview is now online: http://dailyjs.com/2010/08/11/ryan-dahl-part-2/

Inspired by http://dailyjs.com/2015/07/07/the-end/ ?

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 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)_Prev… [2] http://stackoverflow.com/questions/6617499/for-node-js-is-there-a-csrf… [3] http://dailyjs.com/2012/09/13/express-3-csrf-tutorial/ [4] http://www.senchalabs.org/connect/csrf.html

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…