ThisIs_MyName

Running non-trivial code in your head is far too tedious for daily use. I'd much rather add debug checks for invariants when I want to confirm that the code works the way I expect it to.

More of this: https://www.youtube.com/watch?v=yG1OZ69H_-o

> The Netflix/Qwikster you’re paying less but more debacle

What did I miss?

> if you're a GPU manufacturer, make sure the 3V3 supply is tolerant to being externally driven and doesn't backpower anything in the GPU

That's exactly what a "diode on the device side" does.

It hasn't won yet.

https://bazel.build/

We've got at least a year before that happens.

I don't think this "feature" existed a couple of years ago.

Ok so they have hardware support for unaligned accesses, but is it atomic?

I think he's talking about the big unnecessary "Welcome Back!" box that appears randomly.

Please don't: https://news.ycombinator.com/item?id=14785597

Crypto agility is a thing :)

I doubt that .xyz did this intentionally. They just wanted to "capture" 404 traffic by responding to every URL with some content.

If just 1% of real users that hit this 404 page decided to stay on the site and browse related links, that's a huge win.

Doesn't LTO produce even smaller/faster binaries anyway?

Woohoo, I've been using lld instead of GNU ld and gold for a while now and I'd love to have everyone who builds my code do the same.

>just about every piece of non-driver software from the Windows 95 era works unmodified on modern 64-bit Windows

Yep, see Linus Torvalds's rant about this: https://www.youtube.com/watch?v=1Mg5_gxNXTo&t=6m37s (skip to 6:37 and keep watching).

Proggit thread: https://www.reddit.com/r/programming/comments/5t7akn/50_byte...

I prefer "source-to-source compiler": https://en.wikipedia.org/wiki/Source-to-source_compiler

Shit like this is why people don't take HN seriously.

Naw, that's happening because you have a JS thread doing everything. Native code on OpenGL ES is structured very differently.

Cert pinning ignores root certs. This is by design :(

>The Chromium browser disables pinning for certificate chains with private root certificates to enable various corporate content inspection scanners and web debugging tools (such as mitmproxy or Fiddler). The RFC 7469 standard recommends disabling pinning violation reports for "user-defined" root certificates, where it is "acceptable" for the browser to disable pin validation.

There is an official Google extension which does exactly that: https://chrome.google.com/webstore/detail/personal-blocklist...

Care to elaborate?

Font is too big and too thin, IMHO.