On Dec 5, 2017 1:25 PM, "Dave Thaler via iotivity-dev" < iotivity-dev@lists.iotivity.org> wrote:
... Iotivity should really be rewritten to be a clean layer on top of the normal libcoap APIs. +1000 Not just for coap, but because the code is pretty horrible in general. It's no wonder Iotivity has not attracted more core devs. There's me and there's Matt's. Maybe a few other non-corporate visionaries. :) - come out of the closet if you're out there! So here's a proposal for version 2: total rewrite. Sane APIs. Y'know, the kind devs can actually use now, without spending 3 months figuring them out. Actual documentation that is useful. A non-bonkers build system. Fixed and limited scope (no more "hey we got this great idea for our products so we're going to shove it into Iotivity no matter how dumb it is but we can do that since we're a Big Corp., Nyah nyah!") Well I might do all that with OpenOCF but I am just one bear, of little brain. And I think Iotivity should do it. 2 cents, g
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
