Yes, Kai did grow from Chucki. Roman likes to say that the K in Kai stands for Kassebaum but that’s a happy convergence. We chose the name, as we do for all the betas and release names, from a list which gets thoroughly vetted for ‘unfortunate’ meanings in the various languages into which RAD Studio is translated. We did have some others, and one in particular which nearly ended up becoming final (which I was not a fan of, but luckily was voted down by enough of us that it never saw the light of day).
We have secured a long-term deal with “Team Kassebaum” as I like to call Roman and his sons. We have other team members who work on it too - but Team Kassebaum is completely dedicated to Kai, and only Kai (they do not work on RAD Studio etc). Kai also has its own PM. This is one of the reasons why it’s a separate subscription. I absolutely wish it was included in the price, but, right now, we had to charge for it in order to ensure we could get internal funding for it and also make it worthwhile for the Kassebaums to commit resources to it at the level necessary to make it viable, and to evolve.
It is not quite the same as Chucki, especially behind the scenes, and as it evolves to meet changes in the AI providers and how people use AI it will step very far into a new future for it.
We had many people come to us with AI solutions of all sorts of types. There are lots of credible projects out there - for example David Millington’s CodeBot, is awesome. We believe that we should compete by offering what we (Embarcadero) think will work for our typical customer profile - and also to meet the suggestions given to us by various universities and so on.
We spent many months talking to people and listening to criticisms, suggestions, pleadings, rants and raves. Will Kai be what everyone wants? No, absolutely not, and there are plenty of people like @hsvandrew where we may never be the solution to anything (even if I offered him a free license for RAD Studio and Kai) - and I totally get that. But, based on the research we put in Kai is going to be the answer to a very great deal of other people’s wishes and suggestions.
Personally, I think the cloud providers like Anthropic, Google, et al are going to continue to fight it out - and, hopefully that competition will benefit the developer community overall.
What you see in Kai right now is very unlikely to be the same in a very short space of time and this will continue to be the case. It’s inevitable, given the volatility of the development industry. The same is true for RAD Studio, it’s going to continue to adapt to what developers want and how the development industry is morphing - but the settled reality of that; we don’t want to park our trucks on wet concrete. Number one is quality. Number two is the reintroduction of features which were deprecated. Number three is everything else.
I love Delphi. Always have from the very first day I saw it. Nowadays I get to help shape its future. And, yes, AI will help shape that future too.