Tachi VS wttr.in

I've spent the past two years or so working on Tachi (https://bokutachi.xyz/) (https://github.com/TNG-Dev/Tachi), which is a modular tool for tracking rhythm game scores.

Generally, everyone was using their own personal spreadsheets or ancient "just render everything" tables to analyse their scores and progress before this and I'm pretty happy with how it's turned out.

What I'm probably most proud of is that adding support for a new game is adding a new module for it - all of the other features automatically work with it. This turns a "each game needs to have its own full-site tracker" into a "each game needs a configuration for this one tracker", not unlike how LSP simplifies adding language support for editors!

Taught me almost everything I know about scaling a codebase, and despite being a niche tool it's picked up a lot of momentum (2k users, ~3m scores).

wttr.in is unfortunately not accurate in many cities in the world, check their github issues

The difference with weafetch is that it has its own config file which can just be configured and not touched anymore. When using wttr.in with curl, any custom changes you want to get from the output will need to be typed in everytime.

What about https://wttr.in/ ?

The source of the data that are presented: https://github.com/chubin/wttr.in

I don't recommend using wttr.io at all, their current provider shows inaccurate information for many cities, including Berlin. (source)

Oups the last link was incorrect it should have been https://github.com/chubin/wttr.in. I pull the info and store it in a txt file then I reference with cat or sed. That way it's super quick.

See https://github.com/chubin/wttr.in