[davidkircos]

Yeah, it's a valid point.

Our goal isn't to replace production ETL pipelines etc. We are building a place where you can quickly do an ad hoc analysis, share it with your whole team, and iterate on it.

If it's small and works great you're all set. If your work out grows Quadratic just take the Python and SQL code from Quadratic, modify it slightly, and deploy it on more robust infra.

[sitkack]

This is for the room. You understand all of this stuff.

> Our goal isn't to replace production ETL pipelines etc.

Why not? The OP is conflating accidental complexity in current spreadsheet design, there is no reason that you couldn't get a graph of code. Everything becomes production, or mission critical at some point. There is no difference. Production ETL pipelines exist because spreadsheets have historically only run a single machine, hence the whole "big data" definition.

I am absolutely sure you are familiar with https://en.wikipedia.org/wiki/Felienne_Hermans and ZUIs, your work is the intersection of both.

I kinda hope you are pandering to the HN gestalt against spreadsheets. But yes, please do introduce fork/merge/diff (you already have-to to support multiple simultaneous users). As well as property testing.

Aside, I am kinda losing my _, that you pulled all of this off. I absolutely love it. Amazing, hopefully we have a future to thank you.

[elcritch]

Is there a way to view the formula / python code alongside the cells? As in have it permanently visible? So many spreadsheet operations could, maybe should, be tabular operations.

[esafak]

History suggests that successful tools find use outside their conceived niche, so it is a very valid concern.