miniblog.

Rust nightly is now warning about upcoming changes to the type checker. There are some (obscure) soundness holes:
Why did the minidisc not succeed because outside Japan? http://t.co/Djbxm9d5nP
The Creative Apocalypse That Wasn't: http://t.co/AOrXRumJn5 Great data-driven analysis of the effect of the internet on creative industries.
Interesting summary of pain points using Rust in production: https://internals.rust-lang.org/t/production-user-research-summary/2530 (apparently early adopters use emacs/vim/ST/atom)
Discovered that LLVM's lli command has a --force-interpreter option! If you're debugging your LLVM IR, it give significantly more info.
Inspirations For Eve reading list https://gist.github.com/jamii/8957881c8eaa4035f4ae hqs some fascinating papers on language design. Definitely a project to watch!
I keep expecting to reach a point where I'm happy with my .emacs.d. Instead I get better at elisp and experiment with more workflow helpers.
A basic major-mode is just a syntax table and font lock keywords. I've done a revamp of llvm-mode: http://t.co/vqf6Yx1EIv #emacs
Using gdb or lldb with Rust:
On a developer team, the fewer distinct admin powers, the better. Empower your team so anyone can make things better.
Another syntax highlighting package for Emacs that simply calls an external tool! https://github.com/katspaugh/tj-mode (good software should eat itself)
Tracing has comparable performance to partial evaluation, but with significant less implementation effort: http://t.co/BKkZhzFAkv
Tonic is a great REPL environment for node: https://tonicdev.com/ . I think web-based REPLs are still a massively underexplored area.
Neither mobile Firefox nor Chrome (as far as I can tell) have a View Source feature. I think this is a loss though I'd never noticed before.
Good software testing takes a 'guilty until proven innocent' approach.
Showing 5,086-5,100 of 7,549 posts