4 ms·
I've never quite got this. Spend any time writing code that's not using classes and you end up reinventing OOP anyway. "Spend any time" implies substantially m
by Goladus 13y ago
I've never quite got this. Spend any time writing code that's not using classes and you end up reinventing OOP anyway.
"Spend any time" implies substantially more experience than what most beginners possess, hence the term "advanced." "Intermediate" might be a better term in an absolute sense. OO design is something to learn after you understand the basic tools and techniques.
Also, a lot can be accomplished without OOP (for most values of OOP) and even if you're writing de facto OO code, it's not always clear whether using explicit OO language features is a net win or not.
- TazeTSchnitzel 13y agoWell, I think it's better to teach OOP early on to avoid people ending up reinventing it.
- Goladus 13y agoObviously. I strongly disagree. There are many more important things to learn first. OOP can be introduces little by little as it gradually becomes relevant.
- TazeTSchnitzel 13y agoWell, I'd introduce classes after dictionaries and functions, because that's all they are, really.