I’m taking the opportunity to ask something I wanted to know since a long time, but never asked. What is the difference between proton and wine?

I did not double check, but I assume the macro is provided by std (which is allowed to use unstable items internally). This macro can be stabilised, even if the unstable features themselves are not stabilised yet.

Nice to see continuous progress in Rust for Linux, especialy since it’s seems efforts to stabilise Rust features so that RLA doesn’t depend anymore on nightly seems to be fructiful.

I’m looking forward for when a big driver (like ashahi or the Nvdia one) are merged in master. It’s going to be a big milestone.

I’ve exensively used screen, tmux and zellij, and all 3 are fantastic workflow enabler. I can’t recommend enough to take the time learn either one, especially if you work over ssh.

Like how the average computer user is never going to […] install Firefox or whatever.

Not right know but in 2005-2010 (or something like that), the average user was installing firefox because IE was so bad. It used to be at 80% market share IIRC.

git worktree could become your new friend then :)

It’s a question of workflow. Git doesn’t guide you (it’s really workflow agnostic) and I find it easier to taillor CLI to fit my exact need, or use whatever was recently added (like worktrees a few years ago). I have yet to find a GUI/TUI that I’m not frustrated with at one point but everyone has its own preferences.

If you use the git command line (and I do) you should spam git log --graph (usualy with --oneline).

And for your filesystem example I sure do hope you use tree!

It’s so anoying that at $WORK we have multiple git repos with symbolic link that points above their respective .git to each other and need to be in sync. So of course git workree and git bisect don’t work that well…

For those who don’t know (I assume you do), you can git bisect run some_command and git will automatically run git bisect until it finds the falty commit. It’s amazing.

I reread that article every years for a few years. Each time my understanding of git improved significantly.

I reread that article every years for a few years. Each time my understanding of git improved significantly.

It was when I read the git parable.

I have a non-breaking space on my layout since 10 years, and a friend recently added a non-breaking hyphen to his. Appart from search that doesn’t do automatic conversion I didn’t noticed issues.

Looks nice. It has a very good “wooow” effect

That’s a really good explanation. I would just add that I find easier to search for orphans with git log --graph --reflog than using `git reflog directly, especially if it’s one of the top entries in the reflog.

vim can have IDE-like capabilities thanks to lsp and tree-sitter. That’s a real game changer and is quite easy to set-up with something like kickstart.nvim.

Would encoding images in oklch before compressing them using jppeg or whatever is used for video compression helps to have much better dark while still keeping current compression ratio?

This new OKLCH color space looks really nice to use. It’s surprising that it’s really human readable, I wouldn’t have guessed that you could do it for random colors.

I’m a bit surprised. Why does OKLAB gradiant looks better than OKLCH?

Just toebe sure, what’s the name of this new terminal emulator? termkit?