At Meng To's blog. The writing is a little choppy in spots, but this post is thoughtful and the message rings loud and clear: simplifying your interfaces is great, when you're actually simplifying; but if you're not careful you wind up just making something that's sterile and/or confusing. This isn't just another "skeuomorphism vs. minimalism" bit of navel-gazing — he's got something worth reading.
Over at the Forecast.io blog. A great post with some outstanding observations about how what it means to develop apps using the web as your platform. Example:
If you can’t find a way to do something that doesn’t feel choppy or awkward, then just don’t do it. Design your interface around the technology you have, not the technology you wish you had.
Go read it.
jQuery + Knockout + RequireJS = Durandal. I haven't looked at it in any depth yet, but for what it's worth these are some battle-tested names. Worth at least a cursory glance.
Long-ish post by Peter Ledbrook — but worth looking at if you're interested in the future of Grails.
I promise I won't make a habit of linking to Hacker News, but this was timely because this was something that I found myself thinking about while hacking together the Project Management Dev Dice. "What makes
ng-clickany different from
onclick?" There's the usual HN signal/noise to deal with here, but most of the discussion is worthwhile. For my money, where I landed on this was as follows: what makes
ng-clickand its brethren different than the old-fashioned tight-coupling of