As a long time Rails dev who has primarily worked in stacks of Rails APIs and React UIs, does One fit into this category?
I'm excited about local first, but I haven't played around with any of the existing solutions because I was hoping to get my hands dirty with Zero. Thus I come from a point of ignorance. Are there any limitations? Will Zero need adapters to different frameworks or does it hook directly into your running postgres instance so the backend doesn't matter?
Well, at least once Zero is out. It won't have all the stuff Rails has for now, just the data solution (and we have a drizzle-to-zero adapter and setup we'll be recommending as well so you get schema/migrations).
So yea we want to bring the ethos of Rails to JS, but do it in a way that isn't NIH.
Explained a bit more here: https://onestack.dev/docs/introduction#our-full-stack-philos...
Basically Zero will run in the browser and has it's own server which will exist next your database. So you can do all your database management through Rails and there is a section about Custom Mutators where if you need to pipe data through to AR to have it run callbacks, that is possible.
Also - One is not tied to Zero, you can use One for just about any web/native project and bring any libraries you want, we just are making it nice if you follow a certain path.