Michael Walsh wrote:
On Mon, Aug 16, 2010 at 1:01 AM, Mayan Moudgill <ma...@bestweb.net> wrote:
If I may put in $0.02 - that is the main design decisions which I wonder
about. Why not write the core in C and export the functions via wrappers to
each of the 15 languages? Among other things, this would enable any
improvements in the underlying communication infrastructure to be available
to everyone.
Where "everyone" is defined as environments where you can, and are
willing to interop with C.
This might be going off into a tangent about the early design
decisions of this system, but I suspect for most of us using Thrift,
if we had to interop with c assemblies instead of remaining completely
in our languages of choice, we wouldn't even use Thrift in the first
place. That is true for me.
You do realize you are calling code written in C? Unless you're on some
weird system, by the time you get to operations like send and recv, they
are written in C.
How does it matter to you if the Thrift compiler produces
<substitute-your-favorite-language> code that calls Thrift runtime
library code written in C, instead of producing code that calls Thrift
runtime code written in <insert-language> which then calls system
libraries written in C?
