I just leave 'duckdb --ui' running on my computer at all times. While the functionality is great, I'm really not happy that UI itself isn't open source and instead controlled by motherduck. There are many quick and easy improvements that will probably never get made, as motherduck has no real incentive to improve it at this point.
Wonder if this work could be ported as a replacement to duckdb local UI?
I would love for this to be the case... I'm also not a fan of mother's duck ui... Also I created this project like 2 weeks before they launch it (that's why it's named duckui...) I would choose another name but well I had bought the domain already hahaha... But SURE, I would like this to be the best UI ever for all of us... Just need some ideas/help to implement all missing parts...
Curious how tricky it would be to connect this to a local instance of duckdb running in UI mode instead of browser WASM. (Or if that even aligns with your vision of this project). From what I can tell looking just looking at it on my phone your UI seems like a great start to replacing motherduck.
Or it looks like that's basically already supported?! Sorry, I need to spend some time with this, but I'll definitely be testing it out and will provide feedback and/or contributing