Eric Charles

> Why? Because you are introducing hard depenency on a library to numerous packages rather than abstracting and isolating the concerns. Instead of removing for "transaction" lack and break API,...

This is what a few libraries have done. You could get inspiration from e.g. https://github.com/YousefED/SyncedStore

not sure if we understand ourselves... syncedstore hides yjs. If I understand well, you are proposing to use the raw yjs, so exposing yjs instead of hiding.

In that world, can you describe what the future of @jupyter/ydoc (https://github.com/jupyter-server/jupyter_ydoc/tree/main/javascript) would be? If I follow your logic, that package should also dissapear.

Because you would want to use the raw yjs and avoid to deal with transactions, deep observability... as you said. The data structure managed by ydoc are notebook, cells which...

I just say the arguments you are using for modeldb should apply to ydoc. If you want to use raw yjs for collaborative list, maps... you should also use raw...

Hi @doelgonzo I have opened https://github.com/datalayer/jupyter-ui/pull/330 to align the storybook code base to the latest changes. I have also redeployed that branch online. You can try again https://jupyter-ui-storybook.datalayer.tech/?path=/story/components-notebook--lite-python Make sure...

just deployed with micropip which responds better for me ``` import micropip await micropip.install('ipywidgets') ```

> Also, is there a way ti know the notebook is ready for use? You can to listen to the kernel state which are like this (look at the examples...

In https://github.com/datalayer/jupyter-ui/pull/330 I have added to the NotebookLite example the KernelIndicator component.  This is the code, happy to discuss if we could extract higher level API to better expose...