Interesting to see the Language Server Protocol grow, now supporting over 20 PLs: https://github.com/Microsoft/language-server-protocol/wiki/Protocol-Implementations#language-servers (often wrapping existing tools)
miniblog.
Function: addToBasket docstring: "Adds to basket". I see docs like this pretty often! Inform the user, or say nothing (which is reasonable!)
Awesome Emacs package of the day: magithub. Manage issues and PRs from the magit UI!
Emacs is now considering caaar (and the other cXXXr functions) as a subr function rather than part of cl:
Found a reliable way of segfaulting Emacs, without using threads/FFI! https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25684 (last time my Emacs segfaulted was bad memory)
Statically typed PLs can lead to a more interactive experience when writing code: the editor knows more! Not a REPL substitute though.
There's so little agreement on what's 'unacceptably proprietary'.
I believe FOSS is a good thing, so I regret when companies buy FOSS shops and the community forks. But is it economically rational for them?
brag: the Beautiful Racket AST Generator https://docs.racket-lang.org/brag/ (not only generating a parser from BNF, but syntax values with positions!)
32-bit x86 Position Independent Code - It's that bad https://ewontfix.com/18/ (makes a compelling argument for private-by-default I think)
I'm still not sure that coverage percentages are very useful. A good UI that shows which (and when) lines are covered is much more powerful.
Lisp is the only language I'm aware of that uses two comment characters ;; where one would do. I suppose C has // but / is not a comment.
Interactively decompiling bytecode to see if a refactoring is safe! Smalltalk guru meditation: https://www.mirandabanda.org/cogblog/2017/02/07/smalltalk-scanning-and-shcontrol-structures/
GitHub is announcing an upcoming change to its terms and requesting feedback: https://github.com/blog/2314-new-github-terms-of-service (genuinely caring what users think!)
Showing 3,871-3,885 of 7,585 posts