My high school taught Java, but I didn’t get OOP

Yes, the correct sequence of events - one thing at a time, basic programming, then OOP. :-)

Python is not that.

It's not a lot of things, which makes it poor for a teaching language.

No problem. Feel free to ask me questions.

...and riding a bike is easy. Now go watch some kids who have never ridden a bike before and see how that's working out for them.

Oh definitely! Different students have different learning styles - some learn by memorising rules (ROTE), some learn by understanding the rules (Constructivist), some are visual learners, some are better at learning in group activities, etc. - and we have to cater to them ALL, to keep them all engaged (here's WHY we have this rule, here's a video about it, here's a group activity about it, here's a worksheet to practise it). But I was referring to the TOOLS that we use with class. We can't use a tool that the advanced students have no trouble with but the less adept students struggle with - we have to use a tool that the whole class can use, and that's what I meant about catering to the lowest common denominator.

Also some (not all) schools have special classes for gifted and talented (G&T) students. And in fact one class I've had in my time is a class which was comprised of half the students had various learning difficulties (such as being dyslexic), though they weren't told that (these days it's all about trying to keep them in the mainstream as much as possible. So in this class the dyslexic student had a regular student sitting next to him for immediate help with reading anything, which left me free to only need to help him with actual educational issues).

My first language was Basic, and Pascal is definitely better than that as a first language (it's what it was designed for).

That’s silly

Agreed.

This was at a university

As I said elsewhere, I had a much more sensible approach when I went to Uni - we learnt Pascal in first year, and then did OOP in second year, which follows the tradition of only teaching one concept at a time.

Well, I'm only speaking here for my experience with teaching the U.K. curriculum, but probably the same thing applies elsewhere. I know this much - as a teacher, it's very frustrating!

Oh! I just remembered this video. If you wanna know how students can struggle with pseudo code, watch the video. I use this video when I teach algorithms (students are even worse at that than pseudo code).

It looks like pseudo code

P.S. as a teacher, I can tell you I have seen students who even struggle to write pseudo code. It's like trying to teach them Greek (not all students, but some, and we need to cater to the lowest common denominator).

As it is, when we had to teach them HTML, the resources we were given were using PHP at the same time, so I scrapped that and just taught them HTML myself. We never teach more than one concept at a time, so I don't know how these other things found their way into the curriculum/resources.

I just replied to someone else with the same question. Less can go wrong (but in either case a non-OOP language, like Pascal, is a much better starting point. You should only ever teach students one concept at a time).

See my comment