Programmers should obviously be polyglots to some extent, but the question here is if conferences should be. Basically do you want 14 high level introductions to 14 different languages or 14 presentations digging deeper and deeper in to one specific language? I can certainly see advantages to both.
I'm sure even your golfer might be interested in attending a masterclass that only covered putting.
Good point. A conference where different challenges are solved with different programming languages and the people can present their results and conclude the advantages of a certain language for a certain challenge. I believe this always existed in tech world, but, its good that it is getting formalized as a conference. Maybe it could turn out to be like a programming language expo :)
Only if you think of programming languages as an individual golf-club.
Put it this way: Is there a conference for professional basketball, baseball AND ice hockey players? I'm not even aware of anyone who managed to go pro in two of those, not to mention all three.
Most programmers have a preferred domain and language. Once you scale past a pet project and have a decently sized team, specializations start to occur, especially as the code base grows beyond what one person can hold in memory.
I'm reminded of the saying "jack of all trades, master of none".
"Jack of all trades, master of none" applies to situations where the trades are not terribly related to each other. Beyond a certain basic level of knowledge that applies to everything, being a good plumber isn't going to contribute to your being a good farmer, which won't contribute to your being a good therapist. To be sorta good at all those things and others besides requires that you can not have put in the time to master any of them.
Programming languages are different. For one, they all run on the same hardware. For another, the basics of logic and such are the same. And for the coup de grace, we have the well-known acecdata that learning a language of a significantly different paradigm than your "main" language generally improves your ability to program in your "main" language, to the point where I and others routinely recommend to people that they learn (or implement!) other language paradigms as a routine, expected part of their programming career. Learning Haskell to the point you can effectively use it can and will improve your PHP.
In the programming field, I don't think you can be a master programmer without being a fairly effective polyglot, as a bare minimum requirement. That is, if someone claims to be a master but they only have fluency in one language, even if that language is C++ or something, I would not consider them a "programming" master, only a C++ master.
> Only if you think of programming languages as an individual golf-club.
Which is a more accurate analogy than a whole sport.
> Put it this way: Is there a conference for professional basketball, baseball AND ice hockey players? I'm not even aware of anyone who managed to go pro in two of those, not to mention all three.
Among athletes that have gone pro in more than one sport, baseball/basketball seems to be a not-unusual combination:
Michael Jordan is probably the best known example, but also Danny Ainge, Scott Burrell, Nathaniel Clifton, Dave Dubusschere, Cotton Nash, and Bill Sharman.
Hockey is a pretty rare combination with either baseball or basketball.
Felt the need to remind you whippersnappers about Bo Jackson!
I'd also argue that the skills needed for multilanguage competency as a programmer aren't as mutually exclusive as some of the physical traits needed for pro-level athletic talent.
Somebody has already mentioned Bo Jackson. There was also Deion Sanders (at least I think he made into MLB briefly), and long before either Dave DeBusschere, who pitched a season or two in the big leagues and then had a good career in the NBA.
I think they should be (especially as a polyglot myself), but there's also a lot of pressure to super specialize, and not just from employers. Having a network of like-minded developers is an invaluable psychological and career resource.
I'm sure even your golfer might be interested in attending a masterclass that only covered putting.