I don’t see how CompSci departments can ignore Javascript’s vast popularity and the wide array of choices available to developers in regards to libraries, ecosystems and frameworks.
Saying that Javascript is only good for the web is like saying a three iron is only good for golf.
Thomas J Johnson

Because it’s not the role of universities and Computer Science departments to teach a vocation or trade to their (freshmen) students. They’re supposed to teach basic programming concepts and good programming techniques. The best way to do this is starting with a good teaching language. A good teaching language is small and simple and clean, and it gets out of the way of the student so that they can focus their attention on what’s most important, NOT on the peculiarities and quirks of the programming language. See An Open Letter to All Universities.

If after they’ve learned how to program the right way, they wish to pick up industrial languages like JavaScript and C++, they have a solid grounding to do so. This philosophy has been followed by universities and Computer Science departments for decades…until recently. MIT, in particular, is well-known for having taught Scheme — with SICP — to freshmen since the early 199os. Alas, even they’ve been corrupted by this misguided vocational attitude.

ECMAScript may have improved a great deal but it is still far from being a good teaching language. And it is still far from being a good programming language in general. Opinions are very divided, of course, but it’s interesting to note that of all the dozens and dozens of tech articles I’ve published over the past three years, this one has become the most read by far…96,000 views and counting! It has really struck a nerve.

So it would seem that many, many people agree with me: JavaScript is a crap language. Much crappier than Java, Python, C++, PHP, etc.

I hope other schools are not as misguided as Stanford.