CSS Intelligence: Speculating On The Future Of A Smarter Language — Smashing Magazine
This is a really thoughtful look at the evolution of CSS and the ever-present need to balance power with learnability.
This is a terrific spot-on piece by Rachel. I firmly believe that healthy competition and diversity in the browser market is vital for the health of the web (which is why I’m always saddened and frustrated to hear web developers wish for a single monocultural rendering engine).
This is a really thoughtful look at the evolution of CSS and the ever-present need to balance power with learnability.
It seems like the misguided perception of needing to use complex tools and frameworks to build a website comes from a thinking that web browsers are inherently limited. When, in fact, browsers have evolved to a tremendous degree
Why single-page apps are just not worth it:
Here’s the problem: your team almost certainly doesn’t have what it takes to out-engineer the browser. The browser will continuously improve the experience of plain HTML, at no cost to you, using a rendering engine that is orders of magnitude more efficient than JavaScript.
Meanwhile, the browser marches on, improving the UX of every website that uses basic HTML semantics. For instance: browsers often don’t repaint full pages anymore.
A great talk by Matthias on what you can do with web standards today!
A handy one-pager for front-end web developers:
Here are ways to keep track of what you can use, of what’s new in web browsers, and ways you can influence the development of the platform by making your voice heard.
Technically, websites can do just about anything that native apps can do. And yet the actual experience of using the web on mobile is worse than ever.
It is not the job of browser makers to prop up business models, especially ones that don’t even work.
It’s kind of ridiculous that this functionality doesn’t exist yet.
Browser are user agents, not developer agents.
A performance boost in Chrome.