I don't currently use it, but I wasn't aware of it until recently. The issue that we run into at my company is that the exception types generated by Thrift aren't the types that we want to use in our code. As a result, after code generation, we end up writing lots of boilerplate to convert from one exception type to another.
If we could tweak the code generation, then we could avoid all the boilerplate as well as get some efficiency. On Sun, Oct 29, 2017 at 11:54 AM, Randy Abernethy <r...@apache.org> wrote: > I am a fan of tenacious elimination of complexity. Thrift should be fast > and easy. A low level platform upon which you can build your own higher > level abstractions. > > -1 compiler plug ins > -1 recursive data structs > etc... > > --Randy > > On Sun, Oct 29, 2017 at 9:50 AM, Jens Geyer <jensge...@hotmail.com> wrote: > > > > > Not so long ago some people absolutely want it to have ... Thank god > we're > > not in the same position as protobuf (it can't do anything out of the > box, > > you always need plugins) where it is a highly needed feature. > > > > I'd still like to hear the opinion of the people who wanted it, but I > > personally (I can only speak for myself) don't need it. > > > > Have fun, > > JensG > > > > > > -----Ursprüngliche Nachricht----- > > From: James E. King, III > > Sent: Sunday, October 29, 2017 3:38 PM > > To: dev@thrift.apache.org > > Subject: Compiler plug-ins > > > > I'm curious if anyone uses the thrift compiler plug-in feature? It adds > a > > complexity to the build system and the compiler, and if it does not > provide > > value, it should be considered for removal. I'd like to know what the > use > > cases are for having a binary plug-in system when the source code is > freely > > available and modifiable. > > > > - Jim > > > > >
