https://www.npmjs.com/package/auto-install is a fun project: just write require('foo') and foo is automatically installed! Seems like the next logical step.
miniblog.
Tip for magit users: set push.default = current so you can push branches that only have pushRemote set: https://github.com/Wilfred/dotfiles/commit/5402e2e007ee74c4ea9a9019b51357fbfc695a81
Whilst s-expressions are no panacea, they do make some things shockingly easy. Partial application is simple and readable when AST==list.
Linear types make performance more predictable https://blog.tweag.io/posts/2017-03-13-linear-types.html (exploring linear types in Haskell)
Exploring a code viewing tool that allows you to rename functions and update the underlying code. Worried I'm reinventing Smalltalk.
Lispers aren't afraid of C macros, and that leads to remarkable loop constructs that handle circular lists:
I feel like JS can be very readable, but I find myself using 2 space indents due to extensive nesting. I'm going to try using Promises more.
Emacser (noun): a person who spends 45 minutes and 20 lines of code to save one keypress.
Rather than just reporting coverage numbers, codecov has started visualising coverage diff by files!
The lisper in me finds it silly that many PLs don't include a parser in the stdlib. You know the interpreter or compiler has one!
Useless interfaces and interface distillation https://ane.github.io/2017/03/23/useless-interfaces.html (only factor out an interface when you have multiple classes!)
Superb deep dive into how the Rust compiler infers lifetimes: https://stackoverflow.com/a/42639814 (much like type checking)
How do you understand dense lisp code? Code is data, so just walk the tree! I give a walkthrough with lispy.el:
Android is evolving with interesting new APIs in O: https://android-developers.googleblog.com/2017/03/first-preview-of-android-o.html (Wi-Fi Aware will enable proximity chat apps!)
Showing 3,796-3,810 of 7,641 posts