perfectmotherfuckingwebsite VS wttr.in

>However, the expectations for a statically generated site have drastically gotten higher over the years. Readers want (rich) content served fast

No, readers just want content served fast. Nothing beyond simple markdown or static html with some images or video embeds inside.

>Writers want dead simple (but expressive) writing and publishing. They want control over how their writing looks.

Who are those "writers"? If you're making a "static site as a service" perhaps that's a concern.

If you're making your own static site, you can use the simplest Markdown or whatever else you prefer, writing it manually, with or without a generator. You could even use the Motherfucking Website standard (https://motherfuckingwebsite.com/) or the Better Motherfucking Website RFC (http://bettermotherfuckingwebsite.com/) or the Best Motherfucking Website recommendations (https://thebestmotherfucking.website/) or go fancy and use the cutting edge Perfect Motherfucking Website ones (https://perfectmotherfuckingwebsite.com/).

Well in that case you may want to see this then this

⁠https://perfectmotherfuckingwebsite.com/

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