I really value builds, lints and coverage metrics on pull requests. This still feels like an underexplored area though.
There's no Travis equivalent AFAIK for performance. I'd love to have automatic benchmarking on contributions.
miniblog.
Related Posts
The GIMP is the only software tool (AFAIK) where selecting content is an undoable operation.
I think this makes sense: selecting things in a complex image is a much more involved operation than in text.
The read function (lex+parse) in lisp is really handy for building little analysis or metaprogramming tools. The runtime has it, so why not allow users to use it?
However, there's no equivalent for just lexing AFAIK. It's a shame because the same arguments apply!
Calcite is a neat project that uses existing projects to suggest code snippets. https://edelstein.pebbles.cs.cmu.edu/calcite/ (hasn't hit the industry AFAIK)
