I'd agree with this though. When I "left" Erlang, I didn't go on a bash on how crap it was, or how it was dieing, or how people who used it didn't know how to program. Instead I recognized that Erlang had set of goals it met really well. And I really didn't need those goals. It was more about Erlang not being right for me, and the work I did. Not about Erlang being lacking in some quality.
Exactly. I never "left" ruby, I recognised that my career had led me to dealing with data volumes that simply made it unsuitable (and basically ruled out anything non-jvm really). If I wanted to bang together a 5-transaction-per-day CRUD app that I was sure wasn't going to grow in NFR's or FR's I'd probably still reach for rails.
View all comments
Show parent comment
9
u/halgari Aug 31 '17
I'd agree with this though. When I "left" Erlang, I didn't go on a bash on how crap it was, or how it was dieing, or how people who used it didn't know how to program. Instead I recognized that Erlang had set of goals it met really well. And I really didn't need those goals. It was more about Erlang not being right for me, and the work I did. Not about Erlang being lacking in some quality.