Dead googlecode URLs on GitHub
github.com
github.com
* e.g. Uber uses it https://github.com/uber/tchannel-go
But I totally lament the lack of use of tagged releases on GitHub. Sometimes I am looking for versions before some things but after others, for some reason, and it can be very hard to find in a commit list where the code was stable/functional. Depending on the repository, you often can't trust current master to be stable code either.
The thing I really love about the golang vendor/ approach is that the dumbest possible way just works - the code is all there.
Glide gets pretty far away from that. The perfect model (or one which would produce the prettiest git diffs) would probably be a tool which kept the actual vendor'd packages under their own branch forks in the same git repo and checked them all out when you need them, just so vendoring changes wouldn't wind up being huge source tree diffs).
If I could have PRs by default fold vendor/ folders for me, then yeah - problem solved more or less.
I host all my own stuff, but unless I get my shit together and create a set of docs for someone I trust, once I die, my domain, e-mail and all my blogs will disappear and accounts expire and credit card payments fail -- except for whatever wayback might tag important enough to index.
The great libraries of Greece, the technology used to build the Pyramids of Giza, the process the Romans used to make concrete ... all lost. Sure we can reconstruct and examine, but so much is filling in the gaps with guess world. If some alien race found our hard drives and CDs long after we had gone extinct, where would you even begin to decode the data without a rosetta stone?
I have two archive.org webjumps for the conkeror browser:
define_webjump("wayback", "http://web.archive.org/*/%s");
define_webjump("wbsave", function(url) { return "http://web.archive.org/save/"+url; } );Rant from a person who is not in Silicon Valley:
This is so fucking typical of SV. No commitments, no stability, no personal pride in keeping things working for decades if needed. Just the hunt for the next thing, and fuck whatever you worked on last month.
Re-registering the domain would be easy and capturing/selling the credentials would be easy. Once you get an email running a "forgot password" on the "to" address across the top 500 domains might yield something fun. Also catching these specific type domains in drop would be easy with firstname/lastname scan. Cheap as well. Basically fraud based domain squatting.
http://www.cnn.com/2013/06/20/tech/web/yahoo-recycled-email/
I had an account expire ~10 years ago. Somebody else registered the address and used it for several years, then eventually let it expire as well. Last year, I re-registered it, and used it to recover access to an account I created a long long time ago.
<!--[if lt IE 9]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
I know it's only commented out for > ie8. But right now, that's nearly everyone. And I personally still write ie8 compatible code for what it's worth. Stuck on old jquery, old angular, all sorts of shims, etc.
Not saying it is the definitive truth but w3schools puts it at 0.1% < ie9.
Edit: Fixing logic
I've been writing software used in the medical field. And apparently they have a hard time letting go of ie8 and my team hasn't been given the thumbs up to forget about ie8 yet.