plug VS wttr.in

Yes, it’s a bit of a magic argument, but it’s the only unhygienic variable introduced with a Plug dispatch:

https://github.com/elixir-plug/plug/blob/main/lib/plug/route...

Everything else is explicitly passed, AFAICT.

Have you read https://github.com/elixir-plug/plug ? Shows you how to do a GET in under 5 mins.

Coming from the Ruby ecosystem, a lot of this played out similarly to how the Rack[1] middleware conventions developed in the early Rails v1 and v2 days. Prior to Rack there was a lot of fragmentation in HTTP server libraries, post-Rack everything more or less played nicely as long as libraries implemented Rack interfaces.

I don't write Rust professionally, but it was a bummer seeing that this seems to be a place that was figured out (painfully) in ecosystems used heavily for web development--Javascript and Elixir have their own Rack equivalents[2][3]. I hope that Tower plays a similar role to unify the library ecosystem in Rust.

1. https://github.com/rack/rack

2. http://expressjs.com/en/guide/writing-middleware.html

3. https://github.com/elixir-plug/plug

If you're not familiar with it, feel free to check the inner workings of Plug in their documentation. For now, the code above is fairly self-explanatory I hope. All we need to know is that we're using the Plug.Router capabilities and exposing an endpoint /bpi which we're going to use to retrieve our data and to show it.

Well if Phoenix came with the ability to use Sqlite I'd definitely like it a lot better for smaller sites. Maybe if Elixir had something like Sinatra. I guess using Cowboy or Plug could work.

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