|
|
|
|
|
by delinka
2433 days ago
|
|
My sibling comments seem to all want to attribute this foresight to Jobs alone. Jobs had an organization of designers and engineers informing him. Not only informing, but collaborating. He’d express a vision, others would help shape and hone based on existing tech, or based on how they could build new tech, and eventually Jobs would present the vision and solution publicly. And Jobs would take credit. And the process probably didn’t feel collaborative to the other employees. My point is that Jobs didn’t come up with these things all on his own. Other employees were heavily involved. |
|
Jobs was always on the lookout for selling points, the "one more thing." But the impact of objects as a selling point through NeXT and WebObjects on Apple's consumer-focused tech is only skin deep, because creating a comprehensive system would have taken much longer, but it was enough for Jobs to impress people, and provide an essence of an advantage. This was clear in at least early versions of OSX (I haven't used OSX for years), where drag and drop between identifiable objects worked… sometimes. The remaining functionality would have been much harder to achieve, and would have meant something really significant was being built, rather than what became a current generational marketing push. The idea of an object oriented system isn't talked about much anymore, and Apple really focuses on Raskins' ideas for interface, which aren't really compatible since it focuses on one object at a time, rather than a system of objects.