3 ms·
He should just have called it microservices instead of objects.
by bazoom42 2y ago
He should just have called it microservices instead of objects.
- mpweiher 2y agoWell...his original vision was communicating computers, and then scaling that down. Except that Microservices tend to use REST (or something roughly like it) and not CORBA. https://blog.metaobject.com/2019/11/what-alan-kay-got-wrong-about-objects.html https://blog.metaobject.com/2019/11/what-alan-kay-got-wrong-...
- ape4 2y agoOr signal, receptor, effector https://en.wikipedia.org/wiki/Cell_signaling https://en.wikipedia.org/wiki/Cell_signaling
- agumonkey 2y agoThe more I see how microservices evolve the more I think about J2EE remote objects / ejb. A little personal facepalm moment.
- thom 2y agoMicroservices today have all the same problems as OOP, but vastly amplified. My kingdom for some more functional approach to architecture, with services as more or less pure functional transforms, and some sort of extremely well-typed data mesh underneath.
- TZubiri 2y agoThe world runs on microservices, government, agencies, companies, departments, bodies, organs, cells. Sure, reality has problems, and no it won't be solved by trying to understand everything as functions. Welcome to the world
- Phiwise_ 2y agoSmalltalk is a partially-functional language (first-class functions in 1976, inspired by lisp) and also got static typing extensions many years ago.