@gopiandcode Introducing graphics is not dumping down, it's overcomplicating.
What visual tools? Are you talking about scratch now? With processing library you're doing the same exact thing using the same exact tools, it's just your output that is graphical. The 3D engine was just an example of some ridiculous expectation a complete beginner might have, substitute it with literally anything tangible, high or low there is no difference.
teacher: ok kids, lets draw some shapes, let's draw ellipses. You just write "draw ellipse", it's that easy. Let's draw another ellipse right here.
student: *draws two identical ellipses on top of each other and the one underneath bleeds through the edges* wtf is this?
teacher: uhh... (how do I explain this, I didn't even explain arrays yet) uhhh... (wait a minute, I have no idea wtf this is, omg!) It's... just... how it is... it's how screens work... it's how your eyes work... it's an act of god!... it's complicated...
^btw industry standard response here, for your clients and managers, very useful
student: oh, ok... but we're going to come back to this right, and figure it out?
teacher: s-sure... don't worry... (god have mercy on me, what have I done! most of these kids won't come back to this, ever... it's not in this book... it's not in their future job descriptions either... I'm a fraud -_-)
It's dishonest about what you need to be motivated by and excited about to be a happy little programmer. It is a distraction at best.
