One of the things I think a lot about is the fact that OOP *promised* more modularity and reusability.
-
One of the things I think a lot about is the fact that OOP *promised* more modularity and reusability.
The idea was that if an object in a program acted more like an object in real life, then it could be more modular and reusable.
And yet, to use objects in a Classical OOP system usually requires work that feels a lot like microsurgery- You can take in a library's *entire* class heirarchy to use one object.
or carefully resupply an class with its dependencies in its new context.
-
Luci for dyeingreplied to Luci for dyeing last edited by
Even on something as flexible and dynamic as the web platform, if a client sees a button on a site somewhere, I can not "simply" copy and paste it. I must track down all the css, html and javascript, in however many minified and compressed bundles they may exist in
or suppose, even if I were to use the state of the art systems: JSX components, css modules, I still have the problem of resupplying whatever BUILD CHAINS, libraries, hooks, dependencies, and context variables it needs
-
Luci for dyeingreplied to Luci for dyeing last edited by
THIS IS NOT MODULAR. these "components", these "objects", these "modules", these "classes", these arent the actors of the original small talk system. These are fragile beansprouts that die in your fingers the second you try to pluck them and replant them.
And yet somehow HYPERCARD of all things managed to enable this modularity in a way no other OOP system has
except for, flash, before it got infected with class heirarchy ActionScript3 brainworms
Copy And Paste Just Worked.
-
Luci for dyeingreplied to Luci for dyeing last edited by
How did copy and paste just work? how did hypercard and its most popular clone escape the banana gorilla jungle curse?
1. Scripts could be attached directly to buttons/sprites
2. there was *enough* built into the base platform that you did not need to pull in dependencies
3. message passing and events were designed in a way that actually worked to the purpose of self contained modular "actor" objects, that reacted to and responded to their environment like an actual physical object. -
Luci for dyeingreplied to Luci for dyeing last edited by
I think it is worth calling attention, and shaming what specific design choices get made in classical OOP systems to break this modularity.
To document the cultish ideas that destroy this highly useful and yet delicate ecosystems of reuseable actors that respond to their environment.