Make the Web Work for Everyone
As a anecdata-point, Stanford&#x27;s CS 142: Web Applications course was previously focused on Rails, now it teaches a MEAN stack:<p><a href="http:&#x2F;&#x2F;web.stanford.edu&#x2F;class&#x2F;cs142&#x2F;" rel="nofollow">http:&#x2F;&#x2F;web.stanford.edu&#x2F;class&#x2F;cs142&#x2F;</a><p>It requires students to test on Chrome:<p>&gt; <i>Unfortunately, Web browsers are still not 100% identical in their behavior, so Web pages may behave differently on different browsers. For this class, the reference browser is Chrome: your project solutions must work on Chrome, and the CAs will use Chrome to test them. Your solutions need not work on any browser other than Chrome. You may use a different browser to develop your solutions if you wish (Chrome, Firefox, and Safari all have very similar behavior), but please test on Chrome before submitting. We do not recommend that you use Internet Explorer for development: historically, its behavior has been quite different from the other browsers, so things that work on IE may not work on Chrome, and vice versa.</i><p>I have mixed feelings on this. Sure...open web, and everything. But in academia, Chrome is one of the more ubiquitous dev environments to be used...I remember being locked into Visual Studio. And purportedly, the class isn&#x27;t just about job skills...it&#x27;s attempting to teach HTML&#x2F;CSS&#x2F;HTTP&#x2F;JS to students who may have not had real exposure to any of those concepts, on top of Angular&#x2F;Mongo&#x2F;Node&#x2F;Express. Restricting the environment allows at least for more consistent instruction&#x2F;grading.