Yeah, I think we're just on the third wave of style for the Java project:
The first wave was the original Facebook bare C-style structs with
public members.
The second wave was the JDK4-compatible JavaBeans with primitives and
low dependencies.
I think we're deep into the third wave of style, with heavier metadata,
generics and runtime dependencies.
When we added the JavaBeans stuff in the second wave, we preserved
options to for non-Bean generation to preserve backward compatibility.
On 8/30/10 1:34 PM, Bryan Duxbury wrote:
I wish we could have just one style, but I think it's pretty clear that
different people are going to keep wanting a variety of options on or off.
Usually you are separated from other coders' code generator decisions by the
transport, but I don't really know of a way around that with an embedded
server.
