ASN.1 is extremely complicated and hard to implement correctly. All ASN.1 implementations I've seen are either specialized (know how to work only with a very specific message), or slow, buggy and expose equally complicated APIs. Modern systems like protobufs tend to use much simpler encodings & specs which are easier to understand and implement correctly.
I totally get the frustration and such, and not trying to protect Amazon, but: author's web site intercepting browser history to trigger "checkout this content before you leave" when back navigation is clicked is outright evil. Just don't do that, be kind to visitors.
Edit:
1. Dictionary: evil, adj.: morally bad, cruel, or very unpleasant
2. To get the prompt you need to stay around on the page for a while, scroll around, pretend to read it. Triggers at least in mobile chrome browser.
I find it amusing that the advice in the style guide gives a good example contradicting another good example, and contains a subtle bug.
In the "Reduce Scope of Variables", second good example leaks an open file when WriteString fails, because it doesn't follow the own advice of "Defer to Clean Up" if you are curious.
I'm fine with paywalled content overall. I'm not fine with paywalled content on the front page of hn, because it reduces hn utility: I can't see the content.
Wired web site displays annoying "pay us now" banner over half of the page on a phone browser, which cannot be removed, probably due to JavaScript bug. Can't help, but flag this.
May be in reading it wrong, but that page contains another video, couple example snapshots and "why we built this". I still have no idea what all the fuzz is about, and I'm not wasting my time on videos.
I wonder, is there a quick way to learn what's that all about without watching a video? As usual, seems like good old text reading/writing skills are ignored...
A friend of mine who used to work at McDonalds, told that "custom" burgers are always made to order, so he advised that if you want a fresh hamburger, order a cheeseburger with no cheese - you'll get a fresh made to order hamburger and cheese on the side.
The most hard part of PKI is omitted completely in the article: how to deal with revocations (CRLs, OCSP and such). Hope that's not because they "forgot" to do that in their actual infrastructure.