Cog VM is implemented in Smalltalk, translated to a lower level lang: https://www.mirandabanda.org/cogblog/about-cog/ described as a "joy to work with"—high praise!
miniblog.
The C preprocessor can be remarkably difficult to reason about:
Stoke is incredible: it takes a piece of code, generates tests, then fuzzes for equiv instructions to find speedups!
TIL CPU micro ops are not a black box, Intel provides a tool called IACA to help you see what's going on:
When should you use auto in C++? https://herbsutter.com/2013/08/12/gotw-94-solution-aaa-style-almost-always-auto/ argues that it's safer, more readable and more consistent.
Emacs tip of the day: you can use ! to explicitly run git commands inside magit. Handy for deleting large directories: ! rm -r somedir
Great blog post showing how to lower a traditional assembly language to BF:
Understanding Compiler Optimization https://www.youtube.com/watch?v=FnGCDLhaxKU (great talk, Chandler notes 'LLVM does not optimise if UBSan cannot warn on UB')
When does hyperthreading make sense? https://www.agner.org/optimize/blog/read.php?i=6 (it's a great option to have, but no panacea)
I'm really impressed with rustdoc. It produces attractive, searchable, cross-referenced docs. I'm considering writing some literate Rust.
"giving up ownership sells the community instead" https://medium.com/message/diary-of-a-corporate-sellout-587479c215f4 (selling a small startup to an established company is difficult)
Once a language is established, it's rare to see much work on the docs. I'm impressed to see Rust is still polishing
The opposite of syntactic sugar is, amusingly, 'syntactic salt': https://mail.mozilla.org/pipermail/rust-dev/2014-January/008324.html (meaning: intentionally awkward syntax)
ido tip: if the current file doesn't exist, ido searches for similar files. You can undo with C-z, or simply disable
Showing 871-885 of 922 posts