This module provides the API to an HTTP/1.1 compatible client according to RFC 2616. Caching is not supported

During a hype phase like that, an incredible influx of newcomers drop by to see what the fuss is all about. Some will stay, most will leave. Your stay might be in terms of months or years, and in rare cases where you find a home it could last decades. But the vast majority of them will be a continuous flow of serial early adopters who surf from tech to tech, sniffing the best opportunity to gain a competitive advantage by being first to use a type of framework, language, or toolkit.

If only we can get one big project going, then the devs will appear, and it will become self-sustaining. I believe this is patently false, mostly because Erlang has had dozens of killer apps during its biggest hype phase, and yet, the community remained small.

I think now that killer apps are driven by people glutting to an initial hype phase, not the opposite. There is always a smaller, earlier phase of people sniffing out interesting tech, deciding they like it, then building something, and if that something is a killer app, then you do get an even bigger hype phase out of it. People will cargo cult things, and a success story breeds more copycats. The other common thing is a phase of "reinventing the world", where everyone spends their time reimplementing everything that exists, so you get a bunch of announcements about "something but in language."

Erlang's tooling and ecosystem was lacking. People in the Erlang community had self-selected to be those who could tolerate that barren environment, and as such were insensitive to the plight of newcomers.

If like me, you were part of the big initial hype phase, but unlike me, you didn't stick around because a lot of things felt unusable or too tricky, you might want to give it a second try. The ergonomics of the language and its ecosystem have improved drastically.