News

Add new post

Polyfills

Remy Sharp just posted to Google Plus about how he came up with the name of Polyfills. It is fairly obvious but probably something work keeping record of, you all know how rumours can change things!

Original post: https://plus.google.com/u/0/109330852418236875528/posts/3YMEPcAGBny

Where polyfill came from / on coining the term

It was when I was writing Introducing HTML5 http://introducinghtml5.com back in 2009. I was sat in a coffeeshop (as you do) thinking I wanted a word that meant “replicate an API using JavaScript (or Flash or whatever) if the browser doesn’t have it natively”.

Shim, to me, meant a piece of code that you could add that would fix some functionality, but it would most often have it’s own API. I wanted something you could drop in and it would silently work (remember the old shim.gif? that required you actually inserted the image to fix empty `td` cells – I wanted something that did that for me automatically).

I knew what I was after wasn’t progressive enhancement because the baseline that I was working to required JavaScript and the latest technology. So that existing term didn’t work for me.

I also knew that it wasn’t graceful degradation, because without the native functionality and without JavaScript (assuming your polyfill uses JavaScript), it wouldn’t work at all.

So I wanted a word that was simple to say, and could conjure up a vague idea of what this thing would do. *Polyfill just kind of came to me, but it fitted my requirements. Poly meaning it could be solved using any number of techniques – it wasn’t limited to just being done using JavaScript, and fill would fill the hole in the browser where the technology needed to be. It also didn’t imply “old browser” (because we need to polyfill new browser too).

Also for me, the product Polyfilla (spackling in the US) is a paste that can be put in to walls to cover cracks and holes. I really liked that idea of visualising how we’re fixing the browser. Once the wall is flat, you can paint as you please or wallpaper to your heart’s content.

I had some feedback that the “word should be changed” but it’s more that the community at the time needed a word, like we needed Ajax, HTML5, Web 2.0 – something to hang our ideas off. Regardless of whether the word is a perfect fit or not, it’s proven it has legs and developers and designers understand the concepts.

I intentionally never really pushed the term out there, I just dropped it in a few key places (most notably the book), and I think it’s when +Paul Irish  gave a presentation some (many?) months later, directly referencing the term polyfill, was when the term really got a large amount of exposure (I think this was also helped with the addition of the Modernizr HTML5 shims & polyfill page).

First WWW flyer

I have what I think is the first A4 leaflet produced by Tim, that my wife brought back from Hypertext 91′ in San-Antonio Texas (a conf she attended as a Digital engineer working on their own hypertext of that time, called Memex, integrated in DecWindows).

It has on one side a variation of the “Web bus” drawing and on the other side the text from the usenet announce from Aug 91

I put a scan online

Archiving Format

I was poking around in search of good ways to grab pages for preservation, since I feel like “Save as Web Archive” in browsers isn’t really a good long-term solution.  Is there anything better than or otherwise preferable to Web Curator?

(Added 7 June 2012 7:45pm) — The reason I ask about Web Curator is that it appears to save content in the WARC format, which—according to the answers on this Stack Exchange post—is the preferred format for archiving (static) web content.  Is grabbing stuff with wget sufficient?  Should we go with WARC regardless of tool, or is it too much/not enough/not right for us?

Welcome

Thanks for the interest a lot of you have already expressed, on this page and offline. Dan Brickley and I will be the chairs of this group, and in the course of next week we will send a “charter”, or at least a description of the activities and the objectives we’ve thought of when we decided to create this group. Hopefully this description will help start the discussion and figure out what the group will first focus on.

Perfect Timing

I can’t tell you how excited I am about this group’s existence!  I’ve recently started collecting a few pieces of history on my own, and have been slowly gearing up to start documenting the stories of people and events in web history before they’re lost.  To think that a group of like-minded people can help with that is…well, it’s incredibly exciting.  I may have said.

I don’t have the material I’ve collected up anywhere public, but I hope that will change.  When it does, I’ll leave word here.  If anyone has pointers to particularly obscure or otherwise fragile historical works, please let the group know so we can be sure to archive it.

Thanks to Shane Hudson for getting word of the CG to me, and I am really looking forward to what we find together!

Browser Archive

I know the group has existed for about 3 minutes, but I am writing this now before I get distracted by … ooh shiny!

Anyway, I also don’t know if this group will have its conversations here (like the Responsive Image community group) or via email (like the Web Education community group), so I am dropping this here.

Many years ago (15+) I created a browser archive which resides at browsers.evolt.org. In itself it is full of chunks of web history and I suspect might interest this group even if the group tends toward other bits of web history.