All programming is a learning experience. Case in point: I recently spent about three weeks working independently on updating an insurance client’s web app from PHP to AngularJS, only to be told after that time that the client wasn’t interested in using AngularJS. At all.
Frustrating, to be sure, but it turned out those three weeks of work were excellent practice in using this new-to-me framework. When I saw an opportunity to use it on a different, internal project, I was able to dive right in and get it done in three days.
I suppose, in light of that fact, that Google’s other recent announcement that Chrome Frame will be retired in January 2014 shouldn’t surprise me. This is actually a bit of a blow for those of us developers (i.e., almost everyone) who still need to keep old Windows XP computers which rely on IE7 and 8 in mind. Chrome Frame has been an integral part of HTML5 Boilerplate for exactly that reason, and with it gone, we’ll have to resort to either conditional comments or just outright telling them to install a modern browser instead. (If you have to ask why we don’t just standardize on IE8-compatible HTML and CSS, it’s the same reason professional basketball players don’t standardize on Converse All-Stars.)
Every now and then, when things get slow at work, I look for an existing site on the server that needs its code updated and rebuild it. Same design, with a few minor or largely hidden changes, but using minimal HTML5 and lots of CSS. Last week, the Village of Riverwoods, Illinois got picked out for an under-the-hood makeover.
An alternate version of the site was also built when we realized that Blackberry phones don’t support the hashchange event, and at least one of the client contacts used a Blackberry on a regular basis. Both versions obtain their content from the same source using server-side includes, making them maintenance-free and easier for the client to update as needed.