5 ms·
I don't think it's down trending at all. Just look at the most recent Hiring thread on this forum! Based on what I've been seeing, Elixir has been growing fast
by AlchemistCamp 4y ago
I don't think it's down trending at all. Just look at the most recent Hiring thread on this forum!
Based on what I've been seeing, Elixir has been growing faster the past year or two than it was previously. Elixir Forum's posts and active users are going up and that's where people tend to ask their questions, rather than Stack Overflow. In fact, the lack of support from companies like Stripe is the single top complaint I hear. Most users are very happy with the language, tooling and community.
FWIW, I'd like to see a Stripe Rust lib, also. But it's far more important to just be make the guides better for people who aren't using a Stripe API client and maybe even make a guide for making a compliant API client. That way, you can be programming in something truly niche like Janet and still have a great experience with Stripe.
The information is all there, but it takes way more digging than it should to get at it.
- andy_ppp 4y agoI wonder if there is a format for API -> client automation that can be good enough, in the end Stripe have a rest API, with enough description it should be possible. Okay so after a quick google it appears Microsoft are the "Simpsons already done it" of the programming world: https://github.com/Azure/autorest/ https://github.com/Azure/autorest/ It'd probably be a good idea to add an Elixir backend for that and point it at the Stripe's API here: https://github.com/stripe/openapi https://github.com/stripe/openapi
- AlchemistCamp 4y agoInteresting... I've spent a fair amount of time looking at Stripe docs while working on various projects over the years and never seen the openapi link before! Purely in terms of seeing what structs are used in what what on what endpoints, the docs are fine. It's really when it comes to guides that it falls over since they invariably lean on language-specific API clients. This makes it easy to miss how headers are constructed, the required security-related details for webhooks, etc.