[lolinder]

You're occupying a very special niche (typed BEAM language), so if I were you I'd be wary of attributing your growth to your moderation practices. Correlation and causation and all that.

My prediction is that you grow rapidly because of natural interest in the niche you occupy. Your community will get larger and more diverse than you expect in spite of your efforts to keep people out. Then, when you run into your first major point of conflict about language development, the community will be divided on what to do and your efforts to moderate in this way will only fan the flames. Then Gleam will go the way of Elm—it will go back to being something that a very small niche group keeps using, but the bulk of the excitement will go back to Elixir as it slowly starts to occupy your technical niche.

A community with no mechanism for dealing with conflict cannot last long. If being an Elm sounds fine to you—it's not a bad fate after all—then that's fine! Just don't expect more unless you're willing to start developing conflict tolerance in the community.

[lpil]

I think you're misunderstanding here. We have very robust mechanisms for dealing with conflict and we have been successfully employing them for years. We have also consulted with moderators of much larger communities and very confident with how it is going.

Not sure what you mean about the Elm remark. They took the approach you're advocating for and have seen less success than we have financially and in terms of community growth metrics.

[lolinder]

You must have missed when Elm was you [0]. They had far more excitement than you currently do and it lasted a few years.

And they didn't take the approach I'm advocating for (though they didn't take yours either). Their conflict management approach was "we do what Evan says". I'm not saying you're making their mistakes, I'm offering them as a cautionary tale—language success can be fleeting.

> We have very robust mechanisms for dealing with conflict and we have been successfully employing them for years.

If I'm understanding the approach correctly it's basically "we delete it". Feel free to elaborate if that's not what you meant.

[0] https://tjpalmer.github.io/languish/#y=mean&weights=issues%3...

[lpil]

I've been an Elm user since 2016, wrote my start up in Elm, and frequently collaborate with notable members of the Elm community.

Gleam's approach to community and maintainership has almost nothing in common with Elm's, and deliberately so.

[lolinder]

Then you know that this is nonsense:

> have seen less success than we have financially and in terms of community growth metrics.

You're barely starting to pick up speed, and there are so many ways left for you to fail. Much of your recent growth is due to Elixir starting to implement types but not having really arrived yet—sparking interest in the competitor who already has them. How long do you think you can ride that wave?

You've come off in this thread as rather arrogant and self assured, which are good traits for a lone wolf but dangerous traits for a community leader. I've been on the fence on whether to adopt Gleam, but I've honestly seen enough here to know that it's not worth investing the time right now. You may course correct and save the project, but the way you talk about your success as though it's something you achieved in the past through your own efforts doesn't make me think it's likely.

You've also likely seen enough of me to know that I'm not someone you'd want in your community, so I'm content at this point to part paths amicably.

[lpil]

I'm sorry but I don't think you're right here, I've not detected any increase in any Gleam growth metrics when Elixir type related things happen. If anything we see Elixir have a bump when big things happen in the Gleam world, such as their GitHub start count increasing when Gleam v1 went viral.

I do agree though that we're only just picking up speed! Watch this space!