klevdb VS wttr.in

The performance of https://github.com/klev-dev/klevdb is 10x https://github.com/maragudk/goqite so it makes me assume the durability is somewhat lacking. Can you speak to the tradeoffs here around message loss?

I would think that having a small chance of message loss due to writing to an append only log in batches might be a reasonable trade off for many things (if that is how it works).

https://klev.dev

I'm fascinated by the idea of Kafka and wanted to use it like a saas in my own apps, so I made my own take on it. It also doubles as a key/value store, so its useful for a bunch of things. The store itself is OSS and you can find it at https://github.com/klev-dev/klevdb.

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