Your once-a-decade reminder from Kaela Nichols.
Progressive enhancement with handlers and enhancers | hiddedevries.nl
Keeping it simple: coding a carousel by Christian Heilmann
I like this nice straightforward approach. Instead of jumping into the complexities of the final interactive component, Chris starts with the basics and layers on the complexity one step at a time, thereby creating a more robust solution.
If I had one small change to suggest, maybe
aria-label might work better than offscreen text for the controls …as documented by Heydon.
John Resig - Annotated Version of the Original jQuery Release
This is a fascinating bit of web archeology: John has annotated the code from one of the earliest versions of jQuery.
Let Links Be Links · An A List Apart Article
A superb piece by Ross Penman on the importance of being true to the spirit of the web.
A JS framework on every table - Allen Pike
Because in 10 years nothing you built today that depends on JS for the content will be available, visible, or archived anywhere on the web.
(Initially it required jQuery but I tweaked it to avoid those dependencies and Yuri very kindly merged my pull request—such a lovely warm feeling when that happens.)
Awesomplete: Ultra lightweight, highly customizable, simple autocomplete, by Lea Verou
Lea wasn’t happy with the lack of styling and extensibility of the datalist element, so she rolled her own lightweight autocomplete/type-ahead widget, and she’s sharing it with the world.
Designing Experience Layers — sixtwothree.org
The engineering benefits of building websites with a layered approach.
Why, yes, I am talking about progressive enhancement yet again! Why do you ask?
The “Web Application” Myth — Medium
Sensible words from Christian.
Web applications don’t follow new rules.
And frameworks will not help:
A lot of them are not really fixing fundamental problems of the web. What they do is add developer convenience. … This would be totally OK, if we were honest about it.
Client-side MVC’s major bug - TimKadlec.com
I’ve said it before: if your client-side MVC framework does not support server-side rendering, that is a bug. It cripples performance.
The Emularity « ASCII by Jason Scott
That’s Netscape 1.0n, released in December of 1994, running inside Windows 3.11, released in August of 1993, running inside of Google Chrome 39.0.2171.99 m, released about a week ago, on a Windows 7 PC, released in 2009.
But when it comes to trying to navigate the web with that set-up, things get a bit depressing.
Front end and back end - QuirksBlog
The difference between back-enders and front-enders is that the first work in only one environment, while the second have to work with myriad of environments that may hold unpleasant surprises.
The problem with Angular - QuirksBlog
I have doubts about Angular 1.x’s suitability for modern web development. If one is uncharitably inclined, one could describe it as a front-end framework by non-front-enders for non-front-enders.
Implement Server-Side Rendering for SEO · Issue #9938 · emberjs/ember.js
Watch this space.
You Don’t Need jQuery! – Free yourself from the chains of jQuery by embracing and understanding the modern Web API and discovering various directed libraries to help you fill in the gaps.
The tone is a bit too heavy-handed for my taste, but the code examples here are very handy if you’re weaning yourself off jQuery.
Websites of Christmas Past, Present and Future ◆ 24 ways
A superb article by Josh on planning for progressive enhancement—clearly laid out and carefully explained.
HTML5’s “Dirty Little Secret”: It’s Already Everywhere, Even In Mobile - ReadWrite
I’m an advocate for progressive enhancement. Tom Dale is not. But even though we may disagree on that, there’s a lot to like in his sensible, balanced answers to some sensationalist linkbaity questions.
It’s not that the pace of innovation on the Web is slower, it’s just solving a problem that is an order of magnitude more challenging than how to build and distribute trusted apps for a single platform. As we saw on the desktop, it may take a few years to catch up to all of the capabilities of a native, proprietary platform, but in terms of the impact it will have on humanity, forgive me for not losing sleep if we have to wait a few years for it to arrive.
7 Principles of Rich Web Applications
Stop Breaking the Web
Angry, but true.
Don’t lock yourself into a comprehensive technology that may just die within the next few months and leave you stranded. With progressive enhancement you’ll never go wrong. Progressive enhancement means your code will always work, because you’ll always focus on providing a minimal experience first, and then adding features, functionality, and behavior on top of the content.
JS Parse and Execution Time - TimKadlec.com
Using ServiceWorker in Chrome today - JakeArchibald.com
It’s very early days for ServiceWorker, but Jake is on hand with documentation and instructions on its use. To be honest, most of this is over my head and I suspect it won’t really “click” until I try using it for myself.
Where it gets really interesting is in the comments. Stuart asks “What about progressive enhancement?” And Jake points out that because a ServiceWorker won’t be installed on a first visit, you pretty much have to treat it as an enhancement. In fact, you’d have to go out of your way to make it a requirement:
You could, of course, throw up a splash screen and wait for the ServiceWorker to install, creating a ServiceWorker-dependant experience. I will hunt those people down.
[this is aaronland] upload.js
A really handy bit of code from Aaron for building a robust file uploader. A way to make your web-based photo sharing more Instagrammy-clever.
A Fundamental Disconnect, From the Notebook of Aaron Gustafson
Hypertext as an agent of change | A Working Library
The text of Mandy’s astounding dConstruct talk.
44 Medieval Beasts That Cannot Even Handle It Right Now
Look, I would never usually link to a “listicle” on Buzzfeed, but this is all kinds of cumulative mirth.
Tablesaw - A Flexible Tool for Responsive Tables
Those lovely people at Filament Group share some of their techniques for making data tables work across a range of screen sizes.
Meet the Online Tracking Device That is Virtually Impossible to Block - ProPublica
Breach - A browser for the HTML5 era
Personally, I’m all for more browsers. The more, the merrier.
Web 2024 | Robin Berjon
Here’s a dystopian vision of the web in ten years time, where professional developers are the only people able to publish on the web.
The Developer’s Dystopian Future – The Pastry Box Project
My interest in rich client-side apps has almost entirely reversed, and now I’m more interested in doing good ol’ server rendering with the occasional side of progressive enhancement, just like we did it in 2004.
This post resonates with me 100%.
Marginalia | Parallel Transport
Comparing two ways to load non-critical CSS
Scott’s trying to find out the best ways to load critical CSS first and non-critical CSS later. Good discussion ensues.
Using Encapsulation for Semantic Markup on CSS-Tricks
I really hope that this is the kind of usage we’ll see for web components: enhancements for the browsers that support them without a good ol’ fashioned fallback for older browsers.
Introducing drawpath - Josh Emerson
A lovely little from Josh that allows you to draw shapes in a canvas element and then copy the resulting code.
Labelmask | Brad Frost Web
I really like this interface idea from Brad that provides the utility of input masks but without the accessibility problems.
The Sticky Pagination Fixer
If you insist on having a fixed header on your site, please, please, please add this script to your site. I often use the spacebar to page down so this would be a life-saver.
Node School in Brighton
Tom is running a Node School at 68 Middle Street on the evening of March 27th. I plan to attend and finally wrap my head around all this Node stuff.
An interesting pattern for handling complex data tables in responsive designs. It’s a desktop-down approach, but pretty smart.
Great stuff from James Wragg and the gang at Madgex: a way of lazy-loading ads for responsive sites without messing with the ad code.
Why we left AngularJS: 5 surprisingly painful things about client-side JS
You Might Not Need jQuery
Don’t get me wrong: jQuery is great, but for a lot of projects, you might not need 90% of the functionality it provides. So try starting with vanilla JS and only pulling in jQuery if and when you need it.
Why is Progressive Enhancement so unpopular? — All in the head
Like Drew, I’ve noticed some real hostility to the idea of progressive enhancement recently. Like Drew, I don’t really understand where this attitude comes from. It’s not like progressive enhancement prevents you from doing anything you would do otherwise: it’s just another way of approaching the way you build for the web.
I hope I’m wrong, but I suspect that some developers are letting their tools dictate their principles—the tail wagging the dog (where the tail is Angular, Ember, etc.).
Bulletproof Accessible Icon Fonts | Filament Group, Inc., Boston, MA
An in-depth look at using icon fonts without any nasty edge-cases ruining your day.
OriDomi - origami for the web
Type Rendering Mix
Alas, it turns out that it’s reliant on user-agent string sniffing. I guess that’s to be expected: this isn’t something that can be detected directly. Still, it feels a little fragile: whenever you use any user-agent sniffing tool you are entering an arms race that requires you to keep your code constantly updated.
Another good ol’ rant from Tom. It’s a bit extreme but the underlying lamentation with the abandonment of progressive enhancement is well founded.
The (other) Web we lost
John shares his concerns about the increasing complexity involved in developing for the web.
Building for the device agnostic web | Talks | Decade City
Some excellent practical advice on progressive enhancement.
Jeremy Keith – The Power Of Simplicity – border:none
This is the talk I gave at the border:none event in Nuremberg last month. I really enjoyed it. This was a chance to gather together some thoughts I’ve been mulling over for a while about how we approach front-end development today …and tomorrow.
Warning: it does get quite ranty towards the end.
Also: it is only now that the video is released that I see I spent the entire talk looking like a dork with a loop of wire sticking out of the back of my head.
Laying The Groundwork For Extensibility—Smashing Coding
The authors of the Extensible Web Manifesto explain the thinking behind their …uh… thinking.
Prerender - AngularJS SEO, BackboneJS SEO, or EmberJS SEO
I despair sometimes.
Here’s a ridiculous Heath-Robinsonesque convoluted way of getting the mighty all-powerful Googlebot to read the web thangs you’ve built using the new shiny client-side frameworks like Angular, Ember, Backbone…
Here’s another idea: output your HTML in HTML.
isMobileDevice and the death of innocence
Good luck getting that script updated for the thousands of sites and applications, you say to yourself, where it’s laying dormant just waiting to send devices the wrong content based on a UA substring.
I hate carousels, but if you’re going to have one, this progressively enhanced approach looks pretty good.
Progressive Enhancement. Still Alive and Kickin’
Go, Dan, go!
‘Sfunny, I was talking about just this kind of thing at An Event Apart today.
Executing console.log(“hello world”) or window.alert(2+5-20) brings immediate feedback, makes you feel as though you’re getting somewhere and that you are interacting directly with the computer as a programmer. For those of you old enough to own a Spectrum, C64 or Vic20 – BASIC (itself heavily derided) had the same benefit.
Links are not buttons. Neither are DIVs and SPANs by Karl Groves
Not Real Programming by John Allsopp
A terrific long-zoom look at web technologies, pointing out that the snobbishness towards declarative languages is a classic example of missing out on the disruptive power of truly innovative ideas …much like the initial dismissive attitude towards the web itself.
Media Query Events Example
A page to demonstrate the conditional CSS technique I documented a while back.
Progressive enhancement is still important by Jake Archibald
Progressive Enhancement: Still Not Dead. - That Emil
There’s something fundamental and robust about being able to request a URL and get back at least an HTML representation of the resource: human-readable, accessible, fault tolerant.
Oh, no! How horrid! Now Twitter won’t control the “user experience” of that widget!
Instead, the person who actually posted the tweets in the first place gets to decide how they should be displayed. Crazy idea, isn’t it?
Leveraging Advanced Web Features in Responsive Design
A terrific case study in progressive enhancement: starting with a good ol’ form that works for everybody and then adding on features like Ajax, SVG, the History API …the sky’s the limit.
A terrific quiz about browser performance from Jake. I had the pleasure of watching him present this in a bar in Amsterdam—he was like a circus carny hoodwinking the assembled geeks.
I guarantee you won’t get all of this right, and that’s a good thing: you’ll learn something. If you do get them all right, either you are Jake or you are very, very sad.
Deep dive into the murky waters of script loading
Jake casts a scrutinising eye over the way that browsers load and parse scripts …and looks at what we can do about it.
I know jQuery. Now what?
A terrific piece by Remy—based on a talk he gave—on when he uses jQuery and, more importantly, when he doesn’t. His experiences and conclusions pretty much mirror my own, but of course Remy is far more thoughtful and smart than I.
Really good stuff.
Responsive Nav — Responsive Navigation Plugin
How to lose weight (in the browser)
A handy one-stop-shop for tips on improving front-end performance.
The Vanilla Web Diet by Christian Heilman
I like the sound of the book that Chris is writing for Smashing Magazine. It sounds like a very future-friendly approach to front-end development.
You can’t create a button by Nicholas Zakas
Related to my rant on links that aren’t actually links: buttons that aren’t actually buttons.
On layout and web performance by Kelly Norton
This is handy: a look at which DOM properties and methods cause layout thrashing (reflows).
Front-end performance for web designers and front-end developers by Harry Roberts
A really good introduction to front-end performance techniques. Most of this was already on my radar, but I still picked up a handy tip or two (particularly about DNS prefetching).
At this stage it should go without saying that you should be keeping up with this kind of thing: performance is really, really, really important.
Implementing off-canvas navigation for a responsive website by David Bushell
This off-canvas demo is a great practical example of progressive enhancement from David. It’s also a lesson in why over-reliance on jQuery can sometimes be problematic.
phuu/sparksvg · GitHub
Remember when I made that canvas sparkline script? Remember when Stuart grant my wish for an SVG version? Well, now Tom has gone one further and created a hosted version on sparksvg.me
Not a fan of sparklines? Bars and circles are also available.
Audio clips from Full Frontal 2012 | Lanyrd
All the talks from this year’s excellent Full Frontal conference in Brighton, available in audio form for your huffduffing pleasure.
The Vanilla Web Diet | Smashing Coding
I wholeheartedly agree with Christian’s diagnosis of the average web page: it’s overweight to the point of obesity. Fortunately Dr. Heilmann has some remedies.
Fear and Coding in Brighton : Full Frontal 2012
A terrific write-up of this year’s Full Frontal conference, with a descriptive rundown of each talk.
isolani - Web Standards: Web App Mistakes: Condemned to repeat
Some great thoughts from Mike Davies about the strengths of the web, prompted by some of the more extreme comments made by James Pearce at Full Frontal last week.
I should point out that James was being deliberately provocative in order to foment thought and discussion and, judging from this blog post, he succeeded.
The Web’s independence from the hardware and software platform people use is a feature. It’s better than cross-platform frameworks which are constantly criticised for not producing exact native-feeling apps on the multitude of platforms they run on. The Web is above that pettiness.
Going Full Frontal — Acko.net
Steven Wittens, who gave a terrific talk all about maths at last week’s Full Frontal conference, describes his experience at that most excellent event.
Trimming the Fat — Paul Robert Lloyd
A great in-depth description by Paul of how he optimised his site. More of this please!