A pay option like this definitely seems worse than the Firebase backend that AI Studio would automatically use.
Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
51–60 of 83 posts
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#52I made a similar project: https://veneer.leftium.com
You can publish any publicly readable sheet/form (append rows with publicly available form):
- sample sheet: https://veneer.leftium.com/s.1RoVLit_cAJPZBeFYzSwHc7vADV_fYL...
- sample form: https://veneer.leftium.com/g.chwbD7sLmAoLe65Z8
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#53SQLite, SQLite + drizzle with WAL mode, push it to a VPS, do not waste your time on anything else :) Thank me when things become super easy! When things scale, SQLite will still be fine, will fit 99% of the vibe coders needs! When they don't then migrate to what ever!
> When things scale, SQLite will still be fine, will fit 99% of the vibe coders needs! No it won't. SQLite is a poor choice at handling this, period. With all those hacks it still doesn't make any sense over something like PostgresSQL which is designed for that use case. Yet another reason why I dismiss this nonsense of vibe coding.
I accept what you say, my point is for 99% of vibe coded and vibe coders stuff you have no reason to spin up anything more than sqlite, if you grow migrate to postgres, you will have drizzle help you!
A single vps like 1-2 GB ram and 2 CPU can suffice 100s of your projects
SQLite can handle 100s of users easyily
And 99% of vibe coded projects won't grow further than 100s of concurrent users
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#54Don’t really get the purpose for this apart from throw away projects. For vibe coders is it really “hours” setting up a database these days? GCP cloud sql + drizzle ORM is minutes and actually scales unlike a spreadsheet, heck Claude can even write you a deployment script and run it over GCP CLI.
SQLite is enough for 98% of all of these use cases, and 100% of the ones this would appeal to
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#55I like this idea, I wrote a tiny CRM-like thing for my mom a month or so ago (upgrade from a google sheet that I had previously upgraded from an Apple Note) and it uses Sheets as it's backend. She can always go back to the Sheet and lose nothing but the web interface she uses it tailored to exactly what she needs. I couldn't be happier with it and she loves it.
I'll have to remember this for my next little one-off tool.
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#56I think it can be one option to achieve a tiny goal.
Some companies often think that using AWS or GCP is too much of a stretch for a minimum target.
So, it can be a good way to meet their request.
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#57Afaik Google Sheets comes with REST API endpoints by default.
How is this different?
Which scenarios do and which DO NOT require Sheet Ninja?
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#58Did this 9 years ago :o, cached it though.
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#59Don’t really get the purpose for this apart from throw away projects. For vibe coders is it really “hours” setting up a database these days? GCP cloud sql + drizzle ORM is minutes and actually scales unlike a spreadsheet, heck Claude can even write you a deployment script and run it over GCP CLI.
Don't do this guy, cloudsql costs a lot.
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#60[dead]