That's a fair concern and one I've been through myself. I think what we've tried to do is a little bit the opposite honestly - hundreds of thousands of people already use Jupyter for data work and we started with the idea to go where the users are precisely so that they don't have to switch tools.

By making a fork that can be installed in one line of code, we're hoping that we don't make Jupyter user's go through decision fatigue for yet another dev tool. Instead, the idea is to simply make their existing tool better.

Give this a try, I installed it and so far so good. I like that they use RAG on the notebook, so it tailors the responses on what I'm doing. Really great way to get your toes in so far.