August 12, 2015
In his post, Aaron tackles a lot of current debates/topics about the rapid development of features in different browsers and trying to make the Web more of a native experience. Here is a sample of the different things Aaron muses upon:
- New Features vs. Interoperability
- The Web vs. Native
- Change vs. Stagnation
- Cutting Edge vs. Craft
- Developer Convenience vs. User Needs
These are some thoughts that stood out to me near the end of the article that I believe give encouragement to the modern Web designer or developer.
“The sheer volume of new drafts, specs, and concepts (not to mention tooling options) is overwhelming. I’m sure I don’t know half of the features that are in the HTML5 spec, let alone the umpteen CSS3 modules. I probably never will. And I’m ok with that. I’ll pick and choose the bits I’m interested in playing around with and find ways to integrate them into my practice a little at a time. That’s how we learn. That’s how we’ve always learned.”
“We learn and we share. And the tools we have today make it even easier to do so. Not only do we have the usual magazine and blogging outlets, but we also have CodePen and JS Bin and Github and more.”
One of the things I enjoyed about working with Aaron was hearing his thinking about these sort of topics. I really appreciate his balanced perspective in things.
- Ramblings on New Browser Features, Interoperability, Craft, and the Future of the Web – Aaron’s article referenced above
- Stop Pushing the Web Forward – PPK’s article that Aaron is responding to
- If We Stand Still, We Go Backwards – Jake Archibald’s response to PPK’s post
- On PPK’s moratorium on new browser features – Bruce Lawson‘s thoughts
- The Gray Gray Ghost That I Call Home – Chris Coyier’s thoughts related to these discussions that issues are not black and white but shades of gray