I was there from 2006 to 2012. The OS course (I think that's third or fourth semester) was being taught with Active Oberon.
Must have been in 2007 or 2008, so might have changed right after.
Eiffel, Oberon, Event-B are just the most notable examples of things that we were being taught that have never become mainstream.
Yet those are the kind of things universities are great, one get to learn about technologies that changes one's point of view (ideally), something that self taught or professional schools hardly achieve.
I think that my ideal CS education would include 3 things:
1. "We're going to ask you to build real software, with real tools, in a group. Even if it's only for one course."
2. "We're going to ask you to do some theory and write some proofs."
3. "We're going to show you some wild stuff that looks like it belongs on an alternate timeline."
(3) might be something like Oberon, or Racket, or some eccentric faculty project. Or even just teaching all your CS majors Haskell, if you don't have any genuinely eccentric faculty projects to inflict on students.
Innovation is often driven by people who are aware of what might have been.
I think had I been a student with those options I wouldn’t have ended up a lawyer by profession. The American university’s CS, in general, is not that appealing (with a few exceptions obviously).
I think the choice of first language really says a lot about the whole program. More so today than yesteryear, where there was a larger contigent of people with prior exposure to programming.
Do you start more abstract, and if so with functional, imperative or OO underpinnings? Do you intend to switch languages rather soon or later?
The good thing about Oberon, language set aside, is that you could get started without a lot of adminstrative debris. No 80% of the screen covered in an IDE, not even a big ol' "public static void main" that you're told to gloss over.
I can see good arguments for sticking to one language throughout many courses, too. Sadly that often means C++.
> Or even just teaching all your CS majors Haskell, if you don't have any genuinely eccentric faculty projects to inflict on students.
We got taught Eiffel Freshman year, C and Haskell Sophomore year, and after that, whenever a course used another language (Java, C#, C++), the prof just said "you'll pick it up".
(That's leaving out the usual-for-academia-but-still-weird stuff like MATLAB and Verilog)
