RPC predates NSProxy. The "type-safe" version of RPC was CORBA: anybody here use that?
Then there was XML-RPC and then SOAP. The most popular version of RPC is HTTP + JSON, because http isn't blocked at network boundaries and because JSON was friendly to JavaScript in the browser. So... Typesafe lost, stringly-typed won. -- C. Keith Ray * https://leanpub.com/wepntk <- buy my book? * http://www.thirdfoundationsw.com/keith_ray_resume_2014_long.pdf * http://agilesolutionspace.blogspot.com/ > On Dec 7, 2017, at 7:39 AM, Gwendal Roué <gwendal.r...@gmail.com> wrote: > > >> Le 7 déc. 2017 à 16:33, C. Keith Ray via swift-evolution >> <swift-evolution@swift.org> a écrit : >> >> Let's see what disasters were created by people abusing NSProxy, the ObjC >> moral equivalent of a dynamic member lookup type. >> >> I'm not aware of anything. > > > I'm sure you are ;-) > > I'm not expert at all of early ObjC... But wasn't NSProxy the base of > good-old-times RPC? > > OK, in 2017 we know that RPC is dangerous. For example, when `() -> Int` > relies on a network call, it's almost impossible to handle errors. > > But still, is it because an API can be used for bad things that an API is bad? > > Gwendal >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
