I agree. For most CRUD applications, developers should mostly integrating off-the-shelf components, and not constantly be reinventing the wheel. The reason for that being, that customer value (and satisfaction) can be attained by delivering a usable product, and that is what pays the bills at the end of the day. Whether that product is implemented in Python or Elixir is often not visible.
On the other hand, if the task at hand requires a novel approach and using tools that are less frequently used, then that will also be justifiable. Are you developing something that only makes sense to run on the BEAM virtual machine? Go ahead and work with Erlang or Elixir.
Now a third category is programming for enjoyment. In that case you don't work with the constraints of profitability, and you can just have fun. And don't worry too much about Beating the Averages (http://www.paulgraham.com/avg.html)
Enjoyment is much more important than many managers think. Attrition is real, especially nowadays. Enjoying the work, which includes the programming language among other things, plays a big part in hiring and attrition.
I hear you, the last thing I want to feel is dread when implementing something. But recently my priorities have shifted a lot with regards to using the fancy, the new and the shiny. Sometimes I just want to end the day with getting something done and going home with the feeling of satisfaction and having achieved something tangible. Again, context matters with these things.
And with regards to employee retention, I would rather bet big on benefits (paid time off, parental leave, etc.), reasonable working hours (4 days per week), achievable goals, great communication, democracy and good team cohesion. I have a feeling this works for a lot of people. If a language is the only thing that makes you stay, by all means find a place that truly makes you happy in that regard. All I am saying is that there are a lot more variables to worker satisfaction.
> I would rather bet big on benefits (paid time off, parental leave, etc.), reasonable working hours (4 days per week), achievable goals, great communication, democracy and good team cohesion
Those are important factors also. But I would prefer to work 5 days per week and enjoy my work rather than working 4 days and not enjoying it because the PL sucks. Just my 2 cents.
You make an assumption that using “weird” language is new and shiny when those are generally older than “established” languages of today. You can end the day with getting something done in “weird” language too, again generally faster than in some obtuse Java or Go codebase.
On the other hand, if the task at hand requires a novel approach and using tools that are less frequently used, then that will also be justifiable. Are you developing something that only makes sense to run on the BEAM virtual machine? Go ahead and work with Erlang or Elixir.
Now a third category is programming for enjoyment. In that case you don't work with the constraints of profitability, and you can just have fun. And don't worry too much about Beating the Averages (http://www.paulgraham.com/avg.html)