Fixing the booboo I made back in 2009

[remy]

The original version of this blog post told reads to hotlink to the code.google.com project directory to get their HTML5 enable-goodness.

Since then, I've been schooled in the error of my ways, and if you happen to land on (either of) the HTML5 shiv projects, you'll get redirected to this repo. Yay.

But Google being the beast that it is, is shutting down code.google.com. Obviously. ¯_(ツ)_/¯

The impact? Well, the redirect that I mention earlier is great, except it does nothing for this particular link: http://html5shiv.googlecode.com/svn/trunk/html5.js

I think this is the real issue that come 2016, this link will break and likely break a fair sized chunk of web sites (aside: I guess that's a legacy I can kinda be proud of...it's one for the books at least...).

So, I'm proposing at least me pushing a change to the svn repos (on code.google) that includes a console.warn. It's a start, but I think there may have to be a bigger initiative to warn people and get them moving to their own local version, running from a(nother) CDN (wikipedia points to cloudflare today) or if it all possible, use Mr Sir Gentleman Uber Knight @paulirish's mega-connections (given he's 2nd in line to the crown of Google-dom) to get some kind of redirect in place on a permanent basis.

In the short term, any thoughts on the console.warn message?

[Kroc]

Personally, I think alert("ZOMG HAXZORS!!!!"); would get developers to update their code a lot quicker :)

[remy]

No doubt, but I also doubt if the developers are actually looking at the site...rather than the users!

On Wed, 5 Aug 2015 12:32 Kroc Camen [email protected] wrote:

Personally, I think alert("ZOMG HAXZORS!!!!"); would get developers to update their code a lot quicker :)

— Reply to this email directly or view it on GitHub https://github.com/aFarkas/html5shiv/issues/193#issuecomment-127963486.

[jimaek]

Maybe create a web page listing the alternative solutions (bower, npm, CDNs...) and simply link to it in the console. A console message is a good solution and worked great for sockjs when they discontinued their own CDN and motivated all users to switch to a third-party one(jsDelivr).

[dcohenb]

What about throwing in there: alert('STOP USING IE!');