I'm sure these classes still stress heavily commenting your code as well.

"The best way to get a bad law repealed is to enforce it strictly"
Demonstrating that the rules are broken by creating unreadable code that passes the readability guidelines seems a fair demonstration!

As for line lengths, while you can rotate monitors by 90° without too much effort these days, most guys I know work on an unrotated 16:10 or 16:9 monitor, so long lines are actually not that bad.

90º monitors / 9:16 aspect FTW!! I use a 1920*1080 and a 1440*2560.
Also, when using a 16:9 aspect, I always split the IDE down the middle so I can see two files at the same time

No need to strictly stick to the traditional 80 characters (as derived from when we coded via terminals), but it's still a good idea to resort to line-breaks after some point.

I tend to compromise; I keep my comments wrapped at 80, and I try to keep long expressions wrapped, but I will not break things in awkward places, like splitting six parameters into one parameter per line if their names and types are too long.

What on earth is wrong with soft-wrapped lines?