I find it hard to agree with any part of this. To me, it shows a deep misunderstanding of the web—treating the web as just another platform, without understanding what makes it so special.
I think I may have found my polar opposite.
The hilarious obsession with file size is the start of my frustrations with the web community.
I like these design principles for server-side and client-side frameworks. I would say that they’re common sense but looking at many popular frameworks, this sense isn’t as common as it should be.
Josh writes about the importance of using rules and systems as tools without being bound by them.
This amuses me. I am amused.
This is interesting, not because it’s yet another grid framework (which I never use anyway) but because of the way it’s doing layout: with border-box and inline-block, rather than floats. If you’re only serving up your layout styles to browsers that support media queries (which would discount older versions of IE anyway), this could make a lot of sense.
Mark has put together this rather excellent prototyping tool. It’s basically the V from an MVC system. You can easily move stuff around, change data …all the good stuff you want to do quickly and easily when you’re prototyping in the browser.
Jonathan gives a thorough overview of the various tools and frameworks out there to help build native, hybrid and mobile web apps. He also shares his decision-making process on when to build what.
A framework for banging out ready-made responsive designs.
A set of default styles to get started on a mobile-first responsive design.
I’m usually not a fan of CSS “frameworks” but I like the thinking that’s gone into this fluid, responsive system. I particularly like this advice:
Take it apart, steal the parts that you like, and adapt them to your own way of working.
Paul has created a site for tracking usage of the BBC’s GEL (Global Experience Language) visual design language. Nice’n’responsive it is too.
A framework for creating old-school arcade games in the browser, using HTML5.
The BBC have released their JavaScript library. This one is worth paying attention to for its wide browser support base.
Gareth tries to figure out why Django seems to strike a chord with standardistas. It may that the separation of concerns resonates with the methodology of progressive enhancement. Some good comments follow
Here's another CSS framework for grids. It could prove to be very useful for wireframing.
Pulling together a bunch of CSS tricks from a range of sources: reseting, baseline typography and grids (fixed width, unfortunately).
Roll up and get it: hot off the presses; the new version of the Yahoo User Interface library. Happy birthday, YUI.
Christian's wish list for JavaScript libraries.
How much page weight is being wasted on JavaScript. It's time to shed those pounds.
The Spry framework from Adobe looks like it could be worth further investigation. I certainly like the underlying philosophy: lightweight, standards-based, and declarative.
Dan Webb does an excellent job of comparing the big four JavaScript libraries that were discussed at @media.
Douglas Crockford proposes an acid test for JavaScript libraries - "If JSLint finds problems in a library, then dump it and move on to the next one."
An interesting looking lightweight framework for PHP.
The creator of PHP offers an antidote to the profusion of frameworks out there.
This is the plain vanilla look.
You can subscribe to the RSS feed of links.