January 2018 Archive
932.
Long-Term Consequences of Spectre and Its Mitigations
(robert.ocallahan.org)
933.
Why is setState asynchronous?
(github.com)
934.
935.
Alan Turing’s “Can Computers Think?” Radio Broadcasts Re-Recorded
(aperiodical.com)
936.
Why Is 'Affordable' Housing So Expensive to Build?
(citylab.com)
937.
939.
GoPro quits the drone business
(theverge.com)
940.
Jon Skeet earns 1mm rep on Stack Overflow
(stackoverflow.blog)
941.
942.
Tiny, Wealthy Qatar Goes Its Own Way, and Pays for It
(nytimes.com)
943.
Zhaoxin's x86 CPUs
(en.zhaoxin.com)
944.
What Are Capabilities?
(habitatchronicles.com)
945.
Why code that never goes wrong can still be wrong
(pathsensitive.com)
946.
947.
Tinder's lack of encryption allows spying
(nakedsecurity.sophos.com)
949.
Front (YC S14) Raises $66M
(techcrunch.com)
950.
Building a More Secure World with the RISC-V ISA
(riscv.org)
952.
C as an intermediate language (2012)
(yosefk.com)
953.
Decades of movie poster history go online
(sites.utexas.edu)
954.
A Generative Approach to Simulating Watercolor Paints from Scratch
(blog.paytonturnage.com)
955.
How to Measure the Working Set Size on Linux
(brendangregg.com)
956.
Writing a minimal x86-64 JIT compiler in C++, Part 2
(solarianprogrammer.com)
958.
If you multitask, so will your team
(davepaola.com)
959.
Post-mortem of this weekend's NPM incident
(blog.npmjs.org)
960.
Year in Pixels
(year-in-pixels.glitch.me)