miniblog.

← Back to all posts
May 17, 2017 at 02:20
GitHub integration in Atom: https://blog.atom.io/2017/05/16/git-and-github-integration-comes-to-atom.html (I'm excited to see how this develops, it's GitHub's central feature set)
Sunsetting Atom
Sunsetting Atom
We are archiving Atom and all projects under the Atom organization for an official sunset on December 15, 2022.

Related Posts

Aug 7, 2026 at 22:20
171
I've released difftastic 0.70! In this release: * Added Dockerfile and fish shell support * Improved Dart, Emacs Lisp, Erlang, Java, OCaml, PHP, Protocol Buffers and TOML. * A bunch of display and performance fixes.
Release 0.70.0 · Wilfred/difftastic
Release 0.70.0 · Wilfred/difftastic
Difftastic is a structural diff tool that understands syntax. See the manual to get started, and the changelog for historical changes. Diffing Improved diffing performance, particularly when diffin...
Jul 11, 2026 at 23:39
1
I had a third attempt at porting difftastic from Dijkstra to A*, and I've eventually concluded that A* just isn't worth it for the implementation complexity. I had fun writing it up though, and I've even attempted ASCII art for building intuitions:
No longer pursuing A* · Wilfred/difftastic@7479636
No longer pursuing A* · Wilfred/difftastic@7479636
Closes #1007
Jul 9, 2026 at 19:44
1
It's really satisfying fixing crashes in rust-analyzer. You can start from a panic message and dig until you've got a tiny Rust program that triggers the problem. (It's usually an issue with incomplete source files breaking invariants.)
fix: Crash on code actions when an unresolved module is present · rust-lang/rust-analyzer@9d343e9
fix: Crash on code actions when an unresolved module is present · rust-lang/rust-analyzer@9d343e9
Previously rust-analyzer assumed that a module always had an item list, which isn't true for unresolved modules. Handle this situation gracefully instead of panicking, and add a test. AI disc...