Project maturity level update

[cyrilmhansen]

Hi,

I am considering using capnproto-java for a new project architecture.

The Readme mentions since October 9th 2014 that the project is in work in progress state.
Version number is still very low.

When reading the blog, the project seems to be in eternal beta stage but mostly production ready.

Can you clarify the project maturity and eventually the features that are implemented but not production ready yet ?

Is there any reasons to not have a 1.0 version yet ? I understand capnproto cpp itself is not at 1.0 also, but you use different versions.

Thank you + regards
Cyril H

[dwrensha]

Yeah, "work in progress" is probably no longer the best way to describe capnproto-java. I've gone ahead and removed that bit from the README.

capnproto-java supports all of Cap'n Proto's basic serialization features, and my understanding is that at least a few people are successfully using it in production.

I'm disinclined to publish a 1.0 version right now, mainly because I have a some ideas about how to improve the API that I haven't yet gotten around to implementing. In particular, I suspect there is a way to streamline generic type parameters so that, for example, the setFoo() method for generic fields and the StructList.Builder.asReader() method no longer need to take the annoying "factory" type witness argument.