I think the most important thing to realize is that learning a programming language is not the point of the education. The language is the tool they use to provide the education on programming/development/architecture. In my career I have been asked/forced/selected multiple languages. Learning a language well enough to get work done is fairly trivial once you have developed solid fundamentals. Learning it well enough to architect solid well designed solutions takes years of experience working in those languages. I've had to write in cobal, perl, korn, bash, vb6, c, pro c, php, java, groovy, ruby (well in the form of chef), C#, powershell, javascript/node, python (my true love), and finally go. I even had a job at one point that required me to design webpages in PL/SQL. It was terrible, but it needed to be done.
In fact, when I taught programming classes I explicitly did not teach a language. We used psudocode and real code examples in the class, but the students were expected to learn the needed syntax on their own. The value wasn't in teaching the options of a printf statement but rather the reasons and patterns that lead you to printing formatted data to the screen. Of course all work had to be turned in written and functional with the language of the course and I would answer questions if asked.
The techniques used to be successful in almost all of those cases were similar. I was able to leverage my previous experience to quickly get up to speed (we are talking days) and my experience with multiple languages only made me stronger. So don't worry about the language a course uses, worry about the design patterns, methods, and theory you learn.