Fantastic! Congrats on the release, Eric and Andrea!<p>For Elixir devs who want a higher-level interface to Mint, check out Mojito:
<a href="https://hexdocs.pm/mojito/Mojito.html" rel="nofollow">https://hexdocs.pm/mojito/Mojito.html</a>
<a href="https://github.com/appcues/mojito" rel="nofollow">https://github.com/appcues/mojito</a><p>It builds on Mint to offer one-off requests, connection pooling, and a generally friendlier interface than playing telephone with a TCP socket. :) Play around and let me know how it goes!
I like that Mint keeps dependencies to a minimum. I wanted to use the Gun client in the past, but couldn’t because Gun and Cowboy would depend on different versions of Cowlib (this is less of a problem now that Cowboy 2 is well supported in Phoenix). Instead I used HTTPoison, but the way it wraps Hackney makes it a bit annoying to understand and debug, and the pooling can cause problem.<p>Mint looks lower level, but with a clean, well-documented API which should be a great building block in the future. Congrats Eric and Andrea!
It took me a while to figure out whether this is an HTTP client library or a server library. Turns out it is the former. Nice! I like that it's in-process. I wish more Elixir libraries would default to such a design.<p>(EDIT: I had accidentally written "latter" instead of "former" above, causing a bunch of people to correct me, thanks for that)
While I have qualms about the name since this is like the 20th Mint I've heard of now, I'm incredibly excited as to what this has to offer. The control over the underlying process is key to creating beautifully asynchronous applications, and it gives me a lot of node-got vibes in terms of how easy it is to use.<p>And thank god, HTTPS support built in... it never ceases to amaze me why some HTTP libs don't have TLS as a given.
I'm liking the trend of designing runtime-behaviour agnostic libraries in Elixir. We get such powerful runtime capabilities with OTP, but indulged in the wrong context our cool OTP processes can be imposing assumptions onto our users.<p>I'd like to see some kind of generic HTTP contract or REST-API client builder library next so we can have swappable HTTP adapters (e.g. Mint/Hackney). I don't want to depend on a library like HTTPoison or Tesla directly when making a client, instead just generic Request/Response structs or protocols. That way an internal project can use a single HTTP adapter across all REST integrations rather than whatever the library author chose to use.
What is the advantage over Gun? (<a href="https://ninenines.eu/docs/en/gun/1.3/manual/" rel="nofollow">https://ninenines.eu/docs/en/gun/1.3/manual/</a>)
I wish a solid HTTP client and JSON library was a part of the std lib. I feel like all of my apps have HTTPotion, HTTPoison, Poison, and Jason as dependencies.
this library was renamed from xhttp to mint and new name is much more refreshing :)<p>I'm excited to try out this library (or something built on top of it)! In my day to day work I use hackney, it's an awesome lib, but sometimes I struggle with documentation.
A lightweight serverside Elixir framework like this is exactly what I was looking for earlier this week. Phoenix is really clunky in my opinion and pretty foreign (Ruby/Rails-like) coming from a lightweight Flask/Express/Go background.
looking at the library, one of the exciting things (for me) is the existence of stream_request_body. AFAICT there isn't an obvious way to do this in any of the other libraries.
People are the worst at naming products. Why call it Mint when there is already an insanely popular Mint.com financial software. It makes Googling/searching for product relevancy near impossible. It's like try to search for Firefox on Android vs Firefox on a desktop information.