@KentonVarda RPC is the problem
-
-
Replying to @seancribbs
@seancribbs Do you just hate RPC in general or Cap'n Proto RPC in particular?1 reply 0 retweets 0 likes -
Replying to @KentonVarda
@KentonVarda It's not hate. RPC is a flawed abstraction.2 replies 0 retweets 0 likes -
Replying to @seancribbs
@seancribbs I think it's only flawed if it tries to be transparent (look like a local call). Cap'n Proto doesn't do that.2 replies 0 retweets 0 likes -
Replying to @KentonVarda
@KentonVarda I think@seancribbs probably wants unidirectional “fire and forget” messaging in addition to RPC1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@seancribbs "Fire and forget" leaves nowhere to report errors. Very hard to do right. Capnp will support eventually, though.8 replies 0 retweets 0 likes -
Replying to @KentonVarda
@KentonVarda your point at the Rust meetup about fire-and-forget being RPC with an ignored response nearly convinced me ;)@seancribbs1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@KentonVarda Aside from the traditional brokenness of RPC, I'm not convinced I need an encoding lib to provide protocol semantics.1 reply 0 retweets 0 likes -
Replying to @seancribbs
@seancribbs@KentonVarda Cap’n Proto RPC has some pretty awesome semantics1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@KentonVarda I will read in more detail. The way it was presented at#strangeloop put me off1 reply 0 retweets 0 likes
@seancribbs @KentonVarda the sectet sauce like how capabilities actually work and promise pipelining weren’t really covered
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.