1. receiving an answer from a core contributor (valim, McCord, etc)
2. Having the answer become part of the documentation for the language or library
As an aside, the elixir community has a different didactic approach to many others: the documentation in elixir is genuinely instructive (vs a descriptive reference).
As an example, I've been able to download the elixir, Phoenix, and ecto docs and work on an app entirely offline, on an airplane ride, and never felt like I needed to Google anything.
A common elixir answer to "where are all the blog posts" is "read the docs. No, seriously."
This is indeed very common the forums, ha. Also common is for people to actually then go read the docs and be like, "Oh crazy, I'm not used to this!" Not to over-sell the quality of the docs, of course they aren't perfect but they really are particularly good.
That said, with Ecto I just ask it to give me the SQL query. From there it’s pretty easy to manually write the Ecto equivalent.
3.5 is as you describe. 4 isn't perfect but it's good enough, in my experience.
Oh and the chat is better for me than the API. API sometimes gives me the complete opposite of what the chat (correctly) gives me.
I will take your word for it and try.
The other day I used this to create an Elixir wrapper around, appropriately enough, the OpenAI API.
Of course, there's the option of taking an appropriately licensed open source license and making an internal fork... not expecting to really receive updates from upstream after the point of departure.
I've personally been surprised by a pro of having a more intimate community: in my experience, this leads to a higher signal-to-noise ratio in discussions and resources. It feels like what I need to get online is more "condensed".