Compilers are hard. In building my BF compiler with LLVM and Rust, I've hit bugs in both LLVM and the rust compiler!
miniblog.
Upgrade or die: Apple's diabolical re-invention of the version ratchet https://blog.rongarret.info/2016/01/upgrade-or-die-apples-diabolical-re.html (software freedom is a real issue!)
Exciting talk on the current state of Eve, perhaps the most innovative view of computing right now: https://www.youtube.com/watch?v=VZQoAKJPbh8 (demo at 46:50).
By default, make uses 1 process, whereas ninja uses all cores. The former is slow, the latter makes my box unusable. Neither are ideal.
I'm deeply impressed that Rust is not just using LLVM, it's monitoring optimisations and upstreaming improvements!
"It is impossible to safely implement any cryptosystem providing forward secrecy in C."
Nice overview of undefined behaviour in LLVM: https://www.cs.utah.edu/~regehr/llvm-ub.pdf (looks like poison may be removed entirely!)
It's far too easy to just read the comments on HN/lobsters/etc without stopping to think about the content. I'm trying to skip them.
Why are our best tools for composing applications still copy-paste and pipes? Can we do better?
Hyperlinks aren't perfect: they're brittle, and links to specific headings break very easily. Nonetheless, foo.html#bar degrades admirably.
Adding NTP servers to public pools in order to find targets for port scanning: https://netpatterns.blogspot.co.uk/2016/01/the-rising-sophistication-of-network.html (crikey!)
I'm fascinated to learn that compiler plugins exist that earn you about numeric instability! https://github.com/mcarton/rust-herbie-lint (Rust in this example)
The Mythical Man-Finger https://stephenramsay.us/2011/07/25/the-mythical-man-finger/ (discusses the rise of GUIs over CLIs)
Why did EA decide to write their own STL implementation? https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2271.html great discussion of tradeoffs, it's never one-size-fits-all
Showing 4,801-4,815 of 7,584 posts