That would be great if I could just work by myself, happily use Haskell and not worry about bosses mandating something really annoying like Python or Java. In fact, that's one of the main reasons I'm working at a tiny startup right now. But I digress; my main point is simple: since chances are your choice of bullet affects others' choices, especially in corporate settings, it would be much better if it were a good choice.
Well yes. But my point is not that you should use technology X but that just letting you "get back to shooting" could very well be detrimental. In this particular point I'm not defending any particular technology but rather having discussions and disagreements about technologies. After all, you do not program in a vacuum.
I've got no time for bitching but I think serious attempts to study the pros and cons of different approaches are both welcome and needed in our profession.
I'm indifferent, frankly. I think it's valuable to know the pros and cons of different approaches, but most of the time discussion around degrades into unproductive flame wars. It's understandable, though. Dedicating years to becoming good at one approach over another will make you defensive.
But that doesn't mean all bullets are created equal.