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.
- Re: sharing knowledge means sharing control Joe Schaefer
- Re: sharing knowledge means sharing control Joe Schaefer
- Re: sharing knowledge means sharing control Joe Schaefer
- Re: sharing knowledge means sharing control Todd Lipcon
- Re: sharing knowledge means sharing control Joe Schaefer
- Re: sharing knowledge means sharing control Bryan Duxbury
- Re: sharing knowledge means sharing control Mayan Moudgill
- Re: sharing knowledge means sharing control Michael Walsh
- Re: sharing knowledge means sharing cont... Aron Sogor
- Re: sharing knowledge means sharing... Joe Schaefer
- Re: sharing knowledge means sha... Aron Sogor
- Re: sharing knowledge means sha... Joe Schaefer
- Re: sharing knowledge means sha... Bryan Duxbury
- Re: sharing knowledge means sha... Kevin Clark
- Re: sharing knowledge means sha... Bryan Duxbury
- Re: sharing knowledge means sha... Anthony Molinaro
- Re: sharing knowledge means sha... Joel Meyer
- Re: sharing knowledge means sharing cont... Mayan Moudgill