It's really nice having build metadata in your binary (commit date, build date), but it's nice having a reproducible build from a tarball too.
I'm not sure what the best approach is.
miniblog.
@aburka Thanks for the feedback!
Definitely agreed on ours vs theirs, it's really confusing. Unfortunately I'm limited to how the sides are named in the file.
I like the diff3 conflictStyle in git, as it shows the base as well as both sides. I can't guarantee that the base is visible though, and it gives me three files to diff rather than two. Not sure about this case yet.
I'm experimenting with <<<<<<< merge conflict markers in difftastic: recreate the conflicting files and then diff them.
What do you think? Merge conflicts are confusing even at the best of times, but maybe difftastic's UI can help a little.
Running a package manager host for a popular language is really expensive. TIL that Python costs several million dollars per year!
> The display of long lines has been optimized, and Emacs should no longer choke when a buffer on display contains long lines.
Emacs 29 was recently released, and this alone is a great reason to upgrade!
https://www.masteringemacs.org/article/whats-new-in-emacs-29-1
I've created my first standalone Rust library! line-numbers is a simple project for finding line numbers of string offsets, efficiently: https://crates.io/crates/line-numbers
It's factored out of difftastic as it's something I want to reuse elsewhere.
I admire that Chromebooks have an explicit date when they stop receiving security updates. Many devices aren't so clear, so we can't have useful discussions like this: https://arstechnica.com/gadgets/2023/08/no-discounts-or-warnings-for-people-shopping-eol-chromebooks-on-amazon-walmart/
The Stack Overflow moderator strike has come to some agreements! https://meta.stackexchange.com/questions/391847/moderation-strike-results-of-negotiations
This seems like a good outcome, and it should help communication going forward.
I can't think of any other cases where volunteers have successfully run strikes in tech before.
I've been learning how to use Massif, a tool in valgrind for memory profiling. It quickly paid off!
I discovered that difftastic sometimes attempts to preallocate absurd amounts of memory.
Go has a wonderful, accessible discussion of how it does inlining today, the downsides, and the plans for 1.22: https://docs.google.com/document/d/1a6p7-nbk5PVyM1S2tmccFrrIuGzCyzclstBtaciHxVw/mobilebasic
The book 'The Art of the Metaobject Protocol' has two chapters in the public domain and available online!
Chapter 5: Concepts
Chapter 6: Generic Functions and Methods
https://clos-mop.hexstreamsoft.com/
I've released difftastic 0.49! In this release:
* LaTeX support
* Smarter diffing in languages that prefer the outer delimiter (JSON, Lisps)
* Improved parsing for C, C++, Java and Haskell
https://github.com/Wilfred/difftastic/releases/tag/0.49.0
I've learnt a surprising amount by looking at how other people are packaging my difftastic project!
(1) A local copy of the manual doesn't have the version (OpenBSD packaging fixes this).
(2) One of my dependencies has been yanked (Void Linux packaging fixes this).
Tried `just` (the task runner) today, and I really like it. npm has scripts, but `just` works anywhere.
Editor integration is also excellent: you can get by with Makefile highlighting, but in Emacs you can even run everything interactively!
https://github.com/casey/just
https://github.com/psibi/justl.el
Read-Eval-Patch loops and iterating on tests in a faster and more interactive manner: https://ianthehenry.com/posts/my-kind-of-repl/
I'm surprised that there are no ML tools for automatic log highlighting. Logs often have repetitive patterns that lend themselves to distinct colours.
Do any such tools exist?
Old news, but I really like how node v12.17 will speculatively execute pure functions in the REPL.
https://nodejs.org/en/blog/release/v12.17.0#repl-previews
TIL most userspace code in ChromiumOS is now written in Rust! https://chromium.googlesource.com/chromiumos/docs/+/HEAD/development_basics.md#Rust
I've been thinking about making difftastic smarter about context. In principle it understands structure, so I could limit context to the enclosing definition.
However, sometimes it's nice to see surrounding code. Line 644 isn't useful, but maybe 655 is. Opinions?
I've released difftastic 0.48! Highlights in this release:
* Subword highlighting in replaced strings! This is a big improvement in many situations.
* Better Scala parsing
* Better Haskell handling
https://github.com/Wilfred/difftastic/releases/tag/0.48.0
Showing 301-320 of 7,506 posts