3 ms·
So they suck in a bad implementation choice because it looks pretty to them An implementation choice that looks pretty is often a good implementation choice.
by snikolov 15y ago
So they suck in a bad implementation choice because it looks pretty to them
An implementation choice that looks pretty is often a good implementation choice.
- ajross 15y agoExcept, as I was careful to point out, when it's bad. I hoped my example was useful: people think the OO hell ("class Point", "class Length", ...) in Java is "pretty" too. Aesthetics are squishy. It's easy to point to great code and infer that it's beautiful to other great coders. But that doesn't change the fact that most people have pretty awful taste. The affinity of uC hackers to state machines, IMHO, is a good example of this.