Could you elaborate on how OptaPlanner/Timefold wasn't ergonomic?
I 'd love to understand this better, so we can improve it in Timefold Community.
To help deal with new problems, we're creating out-of-the-box quickstarts for common use cases:
https://github.com/TimefoldAI/timefold-quickstarts
As for the Community/Enterprise split - we want to continue the open source project, but we need to eat too :)
Basically, the documentation was set up so that I could come in and do a bunch of the example problems fairly easily, but the part where I model my own problem and execute/solve that was always underserved. Or it felt like that to me anyway. I don’t have a background in the theory, but I can easily see that it could solve my problems if only I could figure it out.
> As for the Community/Enterprise split - we want to continue the open source project, but we need to eat too :)
Yeah, I don’t begrudge you that. It’s just that when I see that multithreading is locked away I just know that the moment I start using the product I’ll find out my toy problems are enterprise scale. Sort of like murpheys law, but for software features.
I 'd love to understand this better, so we can improve it in Timefold Community. To help deal with new problems, we're creating out-of-the-box quickstarts for common use cases: https://github.com/TimefoldAI/timefold-quickstarts
As for the Community/Enterprise split - we want to continue the open source project, but we need to eat too :)
Geoffrey (Timefold co-founder / OptaPlanner creator)