4 ms·
Sadly, I have mixed feelings about this. I feel like an anti-evangelist. I actually like reading complaints about the language...that just means there is less
by throwaway_64000 3y ago
Sadly, I have mixed feelings about this.
I feel like an anti-evangelist. I actually like reading complaints about the language...that just means there is less competition.
- K8s/microservices are better/standard.
- Elixir is too slow.
- Dynamically typed languages suck.
- There aren't enough libraries/ecosystem. And a lot of the libraries look like they are dead.
- No big companies use it for anything.
- It needs a better auth library, something like devise for ruby.
- It is a functional language, and everyone knows they are too hard to use.
- It is too difficult to hire good people.
But now, one of the standard complaints is gone. :(
This means invariably more people finding out that you can build incredible products with tiny teams. :(
Thank you Jose for your leadership and building an incredible community and ecosystem. Hopefully, as the language grows, this stays the same.
- fermuch 3y agoTypings in elixir are and will continue to be optional. This announcement says it is detecting pattern matching and guards at build time instead of runtime, so nothing is changing. And the "upcoming" (still in investigation) new types are totally optional. Only enabled if you use fat arrows. You'll still have the advantages of having the core library and third party libs typed in your IDE, even if you don't use types.
- AlchemistCamp 3y agoIf I understand the comment you’re replying to, the loss is the competitive advantage. I.e., if a desire for static types was keeping a large number of devs away, then this development will lead to far more devs using Elixir. This would erode some of throwaway_64000’s competitive edge as those devs also got the productivity gains of using Elixir.