Jon Paal said:
"balance design choices and justify/rationalise my technical decisions"
That's silly talk.
Only to you I expect! A significant number of experienced developers and
architects I know and many people who frequent these groups will almost
certainly know more than one development language, multiple tools, and
understand about platforms and technologies they rarely utilise.
What does spending time learning unused multiple languages have to do with
design choices ?
Asp.net is not the only framework for building applications in. As an
architect I have to understand the scope and limitations of my technical
choices, tyeing that to resource/skills availability, platform, budget
constraints etc. can make a significant difference in choosing a technology.
If I only know one technology, I cant balance a decision correctly and could
make the wrong decision, or make one biased on only knowing one thing and
limiting my choices.
Are you going to build your ASP.net application in multiple languages ?
Yes, if its appropriate! Why wouldn't I use a DLL developed in VB.NET in a
primarily C# ASP.NET application if it saved time and effort, and had a
multi skilled team. Re-writing that functionality costs money, takes time.
If its easy to support it even though its in another langauge its not a
problem.
Are you saying one language has better utilization in ASP.net than another
?
No, but then if you knew more than one language you shouldn't have to ask
that question!
--
Regards
John Timney (MVP)
http://www.johntimney.com