5 ms·
Haskell was used in the first programming class at university and that was excellent. Some people that already know how to program had to throw their preconcept
by alkonaut 7y ago
Haskell was used in the first programming class at university and that was excellent. Some people that already know how to program had to throw their preconceptions out the window. So everyone was either a novice at programming entirely or at least a novice at functional programming. It wasn’t problem at all. I’d argue most students wrote better code in that class than they did in the imperative/OO classes that followed. Especially the students that weren’t (and likely never did become) programmers.
The thing about imperative and OO programming is that it’s hard to do well. I honestly havent seen more than 1/10 developers write ”good” OO code even after 10 or 15 years as professionals. Large scale OO is a cognitive load that requires extreme focus, skill and talent. I prefer functional (or OO using an extreme functional discipline like all immutable types etc) because I don’t have that talent, focus and skill.
My point isn’t that Haskell should be the language of choice. I think it’s a great language but I think e.g laziness makes it too hard to reason about performance and behavior. Today I’d recommend F# I think.
- Mirioron 7y agoAnd how many people dropped out of CS because of that first Haskell course? I saw plenty of people struggling with Python initially and I know exactly how they felt later when we had to learn Haskell. I think if I had to learn Haskell first, then I would've just given up at the start.
- alkonaut 7y agoI think they deliberately did some really “rough” math and CS classes up front because they knew some would drop out and they preferred them to drop in the first few weeks so someone could take their spot.
- thrower123 7y agoYeah, my university did something similar. The very first computer science course was a bog-standard Java course - this was often an elective that engineers or science folks took also. The first CS-specific course used Haskell, and it probably turned off 75% of the people that tried taking it.
- nh2 7y agoWhere I did my CS degree (Imperial College London) , Haskell is the first language taught (before Java and C). To my knowledge across 4 years there, nobody ever dropped out because of the Haskell. People usually struggled with the maths instead. People also did not have more problems getting Haskell concepts right than linked list modification in Java.
- Mirioron 7y agoThey might not drop out specifically because of Haskell, but I don't see how it wouldn't be a contributing factor. The Haskell course here was pretty much just a struggle for almost everyone that took it.
- Jhsto 7y agoMind the opposite: finishing a bachelor's without ever having to deal with a functional language. I've met a lot of people (at work and post-grad) who have graduated from colleges without an idea of what a functional language is or the concepts behind them. I don't blame them, but its a pity to find so many workarounds in legacy code which could have benefited from functions as parameters and less state in general.
- K0nserv 7y agoMy university(Gothenburg University) did this for the CS course. Haskell does a very good job at levelling the playing field since it was new even to those who had prior programming experience. As I recall about 40 people out of 70 did drop out during the first semester.
- SomeHacker44 7y agoI really hate the concept of "weed out" courses. That is the opposite if what colleges should be doing. We had plenty of them in the sciences almost 30 years ago when I started. We need to make everyone welcome in sciences, not weed people out with overly complex 101 courses. We had Haskell in college too, almost 30 years ago, and even then it was one of the hardest courses at school. This was before IO monad, just as the language was being created in the early 90s.
- alkonaut 7y agoTo be clear: I don't think anyone actually dropped out because of a tiny Haskell class. A lot of people did drop out because they hated math and failed the first couple of courses.
- auggierose 7y agoAnyone who cannot do a Haskell class probably shouldn't become a software engineer. Better software that way.
- tome 7y agoSeems a bit harsh.
- tasuki 7y agoOf course it's harsh! But perhaps also true?
- AnimalMuppet 7y ago
- randomsearch 7y agoLisp (Scheme) was chosen for the same reasons at my uni, but I think is a superior choice as the syntax is so small and it’s very appropriate for teaching.
- preommr 7y ago> Haskell was used in the first programming class at university and that was excellent. I don't think getting started in haskell is that hard. If you're just doing theoretical exercises like building data structures and their related operations then it might even be easier than other languages. Building a bigger application that does things like create a mini game or act as the backend for a web service, you know the cool stuff, becomes a lot harder.
- alkonaut 7y agoYes. I think we wrote a guessing game and a miniature parser etc. The concept of "web service" wasn't invented, sadly.
- nec4b 7y agoProgramming in any language or paradigm is hard to do well. Since vast majority of software that we are using is written in imperative and OO paradigm it is probably safe to say that it doesn't require any special developer power as you claim.
- truculent 7y ago> I don’t have that talent, focus and skill. Same. I'm perfectly happy to fall into the pit of success[1]. 1. https://www.youtube.com/watch?v=US8QG9I1XW0 https://www.youtube.com/watch?v=US8QG9I1XW0