Hacker News Reader

That sounds cool. WebRPC isn't meant to be an "everything to everyone" solution. It's main advantage is simplicity and low overhead. It allows you to quickly and easily build a service tier that is consumable by multiple clients. But if your requirements scale beyond what WebRPC provides, Thrift sounds like a great option.

View on HN

Thrift is such a broken mess I willingly opted instead to fork and update a Java project that exposes xml over http.

Thrift must have been written by people who though SOAP was too easy to use and that developer lives should be made harder.

Completely agree that the thrift stuff is a mess, which is why we only used the one interesting part, the IDL, for our system. These days, proto3 would be viable, but wasn't feature rich enough at the time for our needs when we were evaluating options.

Reply on news.ycombinator.com