Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @dthompson@toot.cat
always tired@project1enigma@chaos.social (2026-09-25 20:55:43)
@dthompson
Not even saying that. Just feels parallel. Like reinventing the wheel (even if not consciously) just hopefully better (but back then the wheel didn't work out so well, was too heavyweight probably which is why SOAP and then REST came to be).
---Reply---
always tired@project1enigma@chaos.social (2026-09-25 20:57:05)
@dthompson
"This protocol allows for networked programming which, with the appropriate tooling, has the convenience of programming against "networked objects" which are little different from any other asynchronous programming in the host language."
Framing network communication as "networked objects" just reeks like the basic approach of Corba: everything on the network is an object (in the OOP sense). Communication is "messaging an object" (again OOP sense, method invocation).
Reply
---Replies---
always tired@project1enigma@chaos.social (2026-09-25 20:58:05)
@dthompson
OCapN/CapTP might just be adding async and native cryptography to Corba (again in spirit, not in the sense of actual technical heritage or *conscious* reinventing).