You certainly know the old tree command.

Or maybe you don't, because it's not installed by default anymore on new distributions.

Why ? Probably because it never kept the promise of an overview of the current directory as a tree.

I present here a macro supported approach for tests in Rust.

When a task isn't instant, you usually don't want to run it on the UI thread.

I present here a simple enough framework to run tasks in background.

Biome is a fast linter.

Bacon is a background code checker.

They're the perfect team to check, fix, and improve your JavaScript / TypeScript / CSS.

You want to use bacon on non rust projects? So do I.

Serde's derive is fantastic but if you want humans to read and write files, you can't just depend on the standard derive for everything.

Having your values, even the composite ones, be written as simple strings is often more convenient.

Broot lets you navigate your filesystem, gives you an overview of any directory, previews file content. It does it by trimming folders in a balanced way, clearly outlining the structure of the tree.

Entering zip archives and navigating them the same way looks like a natural extension, doesn't it ?

Your code is full of lists. And some of them should be sorted.

This post doesn't compare Terminator and Wezterm. This is the help I would have loved to find when starting to try Wezterm coming from Terminator.

How to leverage the Rust compiler to prevent identifier misuse ?

How to go from ec2ba151-7acf-43a9-bb98-6f5331992f42 in your database to "Cust_ec2ba151-7acf-43a9-bb98-6f5331992f42" in your REST/JSON API ?

How to do it at zero runtime cost, with no boilerplate, with a derive macro ?