plug VS react_phoenix

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.

I know that ReactPhoenix uses react-stdio. Looking at top, react-sdtio doesn't use any resources, but the beam does.