6 ms·
Firebase + svelte. Firebase gives you auth, serverless database that you access from the client directly, storage etc. Svelte gives you low overhead, easy to
by jpcapdevila 6y ago
Firebase + svelte.
Firebase gives you auth, serverless database that you access from the client directly, storage etc.
Svelte gives you low overhead, easy to write and easy state management components. it's very close to plain HTML & JS.
- colesantiago 6y agoafterwards you are locked into Firebase.
- adamhp 6y agoIf your MVP succeeds, you should probably throw away the majority of your architecture anyway, so you'll have the debt to address in the future regardless. Why not get up and running quickly?
- adamhp 6y agoI really have been liking the look of Svelte, and used it briefly for a toy project. Have you had success launching anything with it? It still seems a bit immature for my tastes. The last I had heard was that they basically rewrote everything in the most recent major version and that sort of turned me off. Might be totally wrong on that, though.
- jpcapdevila 6y agoYes, I have launched a couple of svelte (sapper) over the last two years. No regrets so far. What they are rewriting is sapper, the next-like framework. It's probably subjective, but I think the ergonomics and low code/noise ratio worth the immature state. Also my team loves it, JR engineers find it easy to learn, even our designer likes to contribute now that we are using svelte.
- Graffur 6y agoAnother vote for Svelte from me. But my set up is: Svelte with Sapper for the front end. It calls API endpoints in a Java Spring backend. I already know Spring very well so this setup is pretty fast for me. Sometimes I use PostegreSQL but at the moment I am using MySQL. I don't plan on using this stack for just the MVP though. If any one of my projects picks up traction I plan to keep this stack.