3 ms·
There's OOP qua Smalltalk/Kay, and then there's OOP qua Java. You're describing OOP qua Java, which is an ugly type of OOP designed for certain performance adva
by philwelch 16y ago
There's OOP qua Smalltalk/Kay, and then there's OOP qua Java. You're describing OOP qua Java, which is an ugly type of OOP designed for certain performance advantages.
- axod 16y agoDon't be ridiculous. 1. It's not ugly 2. It's how CPUs work 3. It's how most people think
- philwelch 16y ago1. By ugly, I mean less mathematically elegant. In Ruby, you say "paul.foo" and get foo from Paul. How Paul gets foo for you is up to Paul. Simple. 2. If you want a programming language that maps closely to how CPU's work, Ruby's definitely not for you. Assembly and C are for you. 3. I can't speak for most people. What I can say is that I can think in C and I can think in Ruby, and it doesn't seem difficult for me.