One brilliant thing about macros is that you can write them, then throw them away if they're not worthwhile. I often end up doing this!
miniblog.
Fascinating history of nodeJS's module system: https://github.com/nodejs/node-v0.x-archive/issues/5132#issuecomment-15432598 -- particularly interesting comments on APIs not right the 1st time.
Interesting machine learning application: detecting abusive messages online!
Coati is a really slick proprietary tool for exploring C++ codebases:
Sometimes when thinking on PL design, I worry about efficiency. Considering the num of successful AST-walking interpreters, it seems silly.
Interesting talk on Fortress: https://www.youtube.com/watch?v=EZD3Scuv02g The parser rejects whitespace that doesn't match precedence!
I still can't make my mind up about using lists for representing syntax. It's great for macros, but ASTs often need more (eg line numbers).
Cuis is the only image-based Smalltalk dialect that supports a PR workflow. https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev I'm hopeful more will exist in future.
Really neat example of using Smalltalk to interactively explore numeric differentiation:
I've just discovered @emacs_gifs by @ocodo -- superb Emacs demos, highly recommended.
TIL about an incredible Microsoft tool that automatically writes code that works with the examples provided:
I happily use GIMP, it's mature, but it looks like it's being developed more actively than ever! 2.9.4 is out:
Blogged: Example Driven Development: https://www.wilfred.me.uk/blog/2016/07/30/example-driven-development/ #emacs
Turns out that it's possible to configure ivy to use exactly the same keybindings as ido! Made my day.
Smoke tests are definitely useful, but they can really throw off code coverage metrics. Showing the number of times executed is a big help.
Showing 4,321-4,335 of 7,584 posts