Conversation

Notices

1. Embed this notice
   niconiconi (niconiconi@mk.absturztau.be)'s status on Tuesday, 04-Jun-2024 01:59:09 JST niconiconi

   Remember when the network was supposed to be the computer and that object-oriented programming across networks was supposed to be the first-class citizen with CORBA and DCOM? Remember when even GNOME and KDE were originally meant to have native networked OOP support? :nadeGranny:

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 04-Jun-2024 02:01:24 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @niconiconi Well I'd say KDE still has remains of it with kparts.
     Funny thing is how massive it all is while plan9 is like sitting there with some applications exposing files ("we have objects, they're called files").
   • Embed this notice
     niconiconi (niconiconi@mk.absturztau.be)'s status on Tuesday, 04-Jun-2024 09:10:35 JST niconiconi

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan@queer.hacktivis.me Meanwhile, to do anything over the network today, you just pack everything into HTTP with no standard serialization, no binding to programming languages, no function prototypes, type checking, language exceptions whatsoever, it's just a big JSON file. It's hard to say which one is a step forward and which one is a step back.
     
     Perhaps the late 90s was the ALGOL equivalent of networked OOP - extremely powerful, seen as silver bullet. Consequence was a system too big and overcomplicated so went out of favor soon, and everything came after that was less powerful, sometimes even as an anti-thesis to that (e.g. BCPL and C), with its own consequence of being too crude.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 04-Jun-2024 09:19:45 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @niconiconi Well there's things like JSON-RPC which can be over TCP/TLS but also WebSocket.
     I'd say it's an improvement, sure it sucks for binary data but for those you can typically refer to an URL, even for livestreams (although I'd say DASH and HLS are quite cursed, specially with M3U files instead of a message-passing socket, but I guess that way it allows for full load-balancing).