<Observable Notebooks 2.0 Technology Preview> <Vi...
# linking-together
m
Observable Notebooks 2.0 Technology Preview

Vibe coding a choropleth map in Observable Notebooks 2.0

😮 1
t
well I am glad they killed observable javascript
j
end of a big ol' stumbling block! and local editing with Vite! lovely infrastructure improvements
more big QoL
And notebooks are now “full bleed”, meaning they extend to the full width of the window rather than being limited to a central column.
t
after 30 mins of playing with it, where I think there are differences between Notebook 2.0 and Lopecode https://bsky.app/profile/larkworthy.bsky.social/post/3lv5vyemd7c2h I have also noticed they have hardened the runtime a little so my previous hack for getting the runtime reference doesn't work. So I need to recrack it if I want to migrate to authoring using that tool
❤️ 3
cracked 😛
🎉 1
k
What does the runtime try to prevent you from doing?
t
Both notebook versions hide a reference to the runtime from userspace. To make your own userspace editor and serializer you need meta programming access via the runtime. The runtime is the spreadsheet engine. Lopecode is built on that reference. I don't think anything was deliberately broken but the front end language semantics have changed which needed some repairs. Still not got everything working but a good chunk is unblocked. There might have been changes to the runtime I can't quite tell yet https://github.com/observablehq/notebook-kit/discussions/20
👍 1