It's not lazy framing, this is what "journalism" is now. Push your agenda as far as you can, misrepresenting as many facts as you like. At the very end of your story -- which >85% will never get to -- walk back your…
> If there was a serious security vulnerability in one version of the software, would users be stuck waiting six months (or possibly forever) to get a patch? They'd probably have to release security fixes for each…
We currently have large excesses of power at nighttime, (production cannot be scaled down and back up in a 24hr period) so the effect could be mitigated by that.
Both protocol buffers and thrift are primarily designed to handle older or newer messages (than your program was compiled with) gracefully. Speed and compactness appear to be secondary goals. (Especially for Thrift,…
Protobufs allow you to define your service, but no RPC system is included.
Good post. Another focus of Thrift (and Google's "protocol buffers", its inspiration) is that modifying your RPCs in a forward compatible way should be easy and have well defined semantics. (Thus the need for a…
I'm missing the back story -- tell me more about Peter Norvig's solver?
It's not lazy framing, this is what "journalism" is now. Push your agenda as far as you can, misrepresenting as many facts as you like. At the very end of your story -- which >85% will never get to -- walk back your…
> If there was a serious security vulnerability in one version of the software, would users be stuck waiting six months (or possibly forever) to get a patch? They'd probably have to release security fixes for each…
We currently have large excesses of power at nighttime, (production cannot be scaled down and back up in a 24hr period) so the effect could be mitigated by that.
Both protocol buffers and thrift are primarily designed to handle older or newer messages (than your program was compiled with) gracefully. Speed and compactness appear to be secondary goals. (Especially for Thrift,…
Protobufs allow you to define your service, but no RPC system is included.
Good post. Another focus of Thrift (and Google's "protocol buffers", its inspiration) is that modifying your RPCs in a forward compatible way should be easy and have well defined semantics. (Thus the need for a…
I'm missing the back story -- tell me more about Peter Norvig's solver?