ctuning / ck

I designed the 1st version of the CK framework as a monolithic application without OO because one of the ideas was to run it natively on bare metal edge devices. In such case it would be easier to convert it into C. However, later, we realized that it's not needed but we got stuck with the original design to ensure stability and compatibility of third-party workflows.

I receive lots of feedback from users asking about a more pythonic version of CK. I believe it makes sense to rewrite CK to be more pythonic with OO programming while keeping backwards compatibility.

I open this project to continue brainstorming and prototyping this idea.