Well it does look beautiful but I don't think I can go back to anything that's un-paged neither, after 17 years of dwm. Also, just watched a bit of an XMonad demo which reminded me how much I love the simplicity of dwm's tiling workflow based on having a master window per page (dwm's tag) because it completely removed the burden of window management for me with barely any configuration, I wonder how I'd do without it ... Probably going to try XMonad just to feel the difference, maybe I'll like it.

What do you mean by un-paged? I just looked at dwm and I don't see that it has anything that other tiling wms don't have. Xmonad, i3, sway... all have workspaces/tags.

Niri also has named workspaces, but when I switched to niri, I realised I only want named workspaces for very few things everything else is just temporary.

Reminds me of this dope lib https://pythonhosted.org/johnny-cache/

Oh wow. That is dope. Thanks for sharing.

Aren't Ultimate Guitar chord progressions user contributed? They often simplify the actual chords in their tabs.

very cool but garmin quatix is hard to beat

> Instead, we took a more direct route - I asked friends at Google (which bought Fitbit, which had bought Pebble’s IP) if they could open source PebbleOS. They said yes! Over the last year, a team inside Google (including some amazing ex-Pebblers turned Googlers) has been working on this. And today is the day - the source code for PebbleOS is now available at github.com/google/pebble (see their blog post).

https://ericmigi.com/blog/why-were-bringing-pebble-back

Ha! Called it.

Ok but why doesn't npm registry actually recompress the archives? It can even apply that retroactively, wouldn't require zopli in npm CLI

Hashes of the tarballs are recorded in the package-lock.json of downstream dependants, so recompressing the files in place will cause the hashes to change and break everyone. It has to be done at upload time.

The hashes of the uncompressed tarballs would be great. Then the HTTP connection can negotiate a compression format for transfer (which can change over time at HTTP itself changes) rather than baking it into the NPM package standard (which is incredibly inflexible.)

But it still can be done on the npm side, right?

I remember when we were using an experimental SDN router, it was 0'ing the MAC address field in the packets, pretty fun to debug

Oooooh that reminds me of when Realtek printed a bunch of NICs with identical MACs.

I ask "what do you think about tests / what's your favorite test framework" and "what is your favorite os / what os do you use at home"

I like to do as much as possible in the type system so I can avoid writing tests.

And ... there is no make test

In EU, electricity price is indexed on gas price, and so, we the gas price is applied to cheap nuclear energy. Also, care do demonstrate how buying Russian oil to India saves Ukraine? Thanks.