4 ms·
Erlang/OTP can evolve as much as it wants (and I'm glad it does), if the ecosystem does not follow it will slow down its adoption/usefulness. OTP does not cove
by linkdd 6y ago
Erlang/OTP can evolve as much as it wants (and I'm glad it does), if the ecosystem does not follow it will slow down its adoption/usefulness.
OTP does not cover all the use cases, you may still need to talk to a database/service for example. Take a look at erlmongo[1], whose last commit is 2 years old.
What I understand from what you're saying is "Erlang/OTP is enough, just reinvent the wheel", which does not seem like a viable solution for any business.
[1] - https://github.com/SergejJurecko/erlmongo
- brudgers 6y agoWhat I am saying is that Erlang is predictable. If it ships with a library that library will almost certainly be maintained ten years from now. And it will probably have been written by people with many years of Erlang experience. It supports OBDC for SQL databases and has Mnesia built in. But what about Mongo? Mongo says it has OBDC support. https://docs.mongodb.com/bi-connector/master/reference/odbc-driver/ https://docs.mongodb.com/bi-connector/master/reference/odbc-... In the Erlang ecosystem dependencies on random GitHub repositories is a bit of a code smell.