1,291 karma · joined November 16, 2010
If I'm not mistaken, this is more or less the approach used in Knockout and AngularJS.
Wouldn't it be much more efficient to create a view just once by setting innerHTML, and then update it using the DOM (setting attributes, classes, innerText, etc.)? Surely this would reduce GC pressure, reflow events, and so on.
I'm seeing "use templates for everything" in most Backbone tutorials and projects, and I can't help but think that this is an anti-pattern.
Looks like the button locations are fixed for now, but they're hoping to make them adjustable in the future.
- allow sorting by rating, year, title
- allow switching between "All Critics" and "Top Critics" ratings
- show additional movie information (summary, etc.) on hover for desktop users
I don't think that works for everyone. I can read an issue of The Economist -- which primarily has a clean, linear layout of two or three columns per page -- basically cover to cover. But take something garishly laid out like Esquire, and my brain and eyes start to revolt after a couple of pages.
The grammar nerd in me is also impressed how, for two years, no one managed to notice that the repeated phrase "we'll lay," although it rhymes in context, uses completely the wrong verb. (It should be "we'll lie.")
I've been using Picasa Web to back up photos by syncing it with the desktop Picasa application. But not all photos that one may want to back up are of adequate quality to publicly share in the same album.
This means that instead of just being able to select which photos in a folder are public and which are private, Picasa users will still have to create new albums and reupload all the photos they explicitly want to share. This makes photo sharing on Google+ no less tedious than on Facebook -- when it had the potential to be much, much easier.
Isn't that what we already had with standard OS window managers, before some applications (like browsers) started using their own internal window management (MDI and tabs)?
Also, purely tabbed window managers (and similar interfaces, like on iOS) have the disadvantage of not allowing user multitasking, which is a huge step backwards in UX. See this article: http://ignorethecode.net/blog/2011/03/04/multitasking.