Emacs tip of the day: use (interactive "*") for commands that edit the buffer, so they show a helpful error if the buffer is read only.
miniblog.
What if Smalltalk had won on Linux, instead of C? https://thoughtstorms.info/view/smalltalkunix (technology popularity is very path dependent)
clang-cl can now compile Firefox on Windows! https://ehsanakhgari.org/blog/2016-01-29/building-firefox-with-clang-cl-a-status-update (LLVM increasingly works *everywhere*)
Apparently, to make a successful language:
1. Good semantics
2. Thorough tests
3. Great tooling
4. Grow a beard!
I think it's been several years since I had a spam email in my inbox (or vice versa). I'm amazed how far we've come.
100 Rust lints in clippy! https://llogiq.github.io/2016/01/28/hundred-lints.html (makes Rust a delight, and regularly adds new suggestions).
Crux https://github.com/bbatsov/crux is a fantastic collection of Emacs conveniences. You've probably reimplemented several of them (I have)!
Nifty talk of an 'org-mode meets prolog' knowledge system https://www.youtube.com/watch?v=voG5-15aDu4
Compiling LLVM can be slow (20 mins on my little box). Luckily, there are pre-built binaries you can use to bisect!
Compilers are hard. In building my BF compiler with LLVM and Rust, I've hit bugs in both LLVM and the rust compiler!
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!
Showing 841-855 of 922 posts