There does seem to be a bit of a community fracture between rebar-centric-world and Erlware-world. I'm not sure I really understand it's origins, or why it persists.

It would absolutely benefit Erlang to heal over this gap -- not that having separate tools is a bad thing at all, but the fact that both ecosystems often seem so blissfully unaware of the other :)

The reality check: for the most of github-hosted erlang projects no one seems to use erlware..