Wow the comments here certainly seem to be against allowing developers any input in the tools they use. I guess you all are part of the reason I have to use Java 7 and outdated versions of Angular in my day job no matter their applicability to the problem domain and have no input in those decisions.
I agree that total anarchy is bad in the workplace, but don't you think that the people using the tools should have some input in choosing the tools?
I, for one, want to see something beyond the shiny-toy syndrome when I talk to a team member about why we need to use the tool/technology/framework/library in question. I'm all for personal improvement, and every technology, regardless how different it is, that we learn/become familiar with makes us better professionals. But sandbox to production is a long way. Keeping things simple has its merits.
I agree that total anarchy is bad in the workplace, but don't you think that the people using the tools should have some input in choosing the tools?