With links about node.js, what kind of programming types are there, why you shouldn’t use (or rely) on jQuery and more.
Even Better In-Browser Mockups with Node.js · An A List Apart Article
Wouldn’t it be nice if we could go from just designing layouts and interactions to designing the whole client side of the application during the same process?
Node at Work: A Walkthrough
Rather than figuring out all your requirements and API schemas just to design your comps with mockup content hard-coded and server interactions faked—only to throw it all away when you go back and implement things “for real”—you can use Node.js to skip the hard-coding and produce client-side code that’s ready for beta at the end of the design stage.
- An Introduction To Programming Type Systems | Smashing Coding
Explaining loosely and strict, among other things.
There is a whole world outside jQuery and it's smaller :)
- Porting from jQuery to Zepto
Some pointers to move from jQuery to Zepto, it ain't too hard.
Even jQuery isn't jQuery anymore :).
- jQuery builder
jQuery Builder lets you easily build a custom version of jQuery that just includes the modules you need. But still it stays too big for my taste...
- 5 Things You Should Stop Doing With jQuery
And I think we all could come op with 25 more points we shouldn't be doing anymore.
- I know jQuery. Now what?
Great article by @rem, who will be talking at mobilism.
- Chris Love's Official ASP.NET Blog : Why Its Time to Sunset jQuery
One more article on how to stop using jQuery.
But really we all should stop just using jQuery, it’s way too big for most of the times that we use it. Yes, it’s fast and easy to develop with, but our users don’t fregging care. And it’s for them that we really build stuff, so go and tell your clients that speed is key.