1–10 of 48 posts
I think this is probably right, but I'm wondering what else you've built in Erlang. Was it a good fit? Why or why not?
It was a tedious, frustrating experience, even though you'd think it would be the perfect language.
It ended up being too slow (probably because of all the string processing)
In my entire programming career, I've never before had to join a mailing list and ask questions to get things done, that should tell you something.
It was a great fit. It lacks Unicode processing capabilities by default, but there are a few open source libraries for that. The only thing I dislike about Erlang is the poor string manipulation and lack of clean structures (Erlang's records are an ugly hack IMO).
Francesco
Great fit. OTP process restart characteristics. Per-tenant process separation. Process abstraction, in general, rather than threads. Finite state machine behaviors. Live code upgrades. Mnesia database.
Only real downside was it took the rest of the team a bit of time to become effective in Erlang... about 4 to 6 months.
I built a very specialized mail server (MTA). It was a tedious, frustrating experience, even though you'd think it would be the perfect language. It ended up being too slow (probably because of all the string processing) In my entire programming career, I've never before had to join a mailing list and ask questions to get things done, that should tell you something.
It's a perfect fit.
Banking systems, both retail and commercial. Logistics. Embedded. Clusterware. Telecoms. Robotics, AI. When it comes to messaging, don't forget RabbitMQ and all the SMS systems. Francesco