JavaScript surprise of the day: [2] * 3 == 6.
miniblog.
If twitter can be microblogging, then GIFs are mico screencasts. They're a brilliant way of showcasing Emacs packages (working on some now).
Emacs tip: if you have a great keyboard macro, but always do the same thing after, you can extend it. C-u F3.
I'm often surprised by the effectiveness of a good README. It brings huge clarity and steers development. It may be GitHub's best feature.
Skimming the docs for lens.js: https://www.npmjs.com/package/safety-lens makes lenses look rather like lisp's setf to me. Is this superficial or deep?
It is so difficult to mix a good REPL (late binding everywhere!) with an optimising compiler (inlining etc). Do any langs do this well?
The remarkable success of Go, despite all the critiques, make me curious enough to try it. I suspect the tooling quality wins users over.
I'm considering using my own builds of Emacs simply because the links to C source code work. I wish distro packages had this.
I've added colour to the minibuffer propmt in the excellent visual-regexp.el!
Scheme rather encourages you to write an interpreter. JS is the total opposite: the engineering effort is intimidating.
Amusingly, no docs are available yet for the ARMv8.2-A arch, but we can see its new features through LLVM patches!
The GCC wiki has a scary list of all the arithmetic transformations that don't work in compliant floating point C:
When programming python, I miss the ability to advise functions. Decorators are like around-advice, but often after-advice is sufficient.
If you ever force push with git, you should really use --force-with-lease to avoid accidental clobbering. If you use magit, it's automatic!
Showing 4,891-4,905 of 7,549 posts