I recently tried Google's cloud functions for backend and firestore for database on a decently sized project. I think it is a good fit for quick small projects and a good experiment if you don't mind a small learning curve. The minor shift in design patterns took me a while to adjust.
Pros:
- Setup is pretty quick, you can move quickly from scratch.
- Deployment is painless.
Cons:
- Firestore is NoSQL which is a huge caveat.
I had to scale the project and add some features later on. Faced some bumps here and there but nothing major (since firebase is still under development). AWS also has similar offerings (lambda, hosted DB etc.) in the same space. I haven't tried them out but look forward to doing so.
For frontend use Vue 10/10 especially if you're looking to put together something quickly. I felt Vue provides a lot more room for "hacking" quick solutions(and improving on top of it later) compared to Angular or even React.
I only prefer this stack for "reactive" web apps though that have a lot of dynamic components. For a traditional website I'd still go with jQuery/Django/SQL.
It's similar in price to Jetstrap, and Jetstrap went under. I think $6 / month or $60 / forever seems fair -- and honestly I'd be worried it's not enough money.
When I use a tool for work, I want them to charge enough to stay in business so they can 1) continue to exist (and I don't have to look for a replacement), and 2) continue to make improvements.
I can think of a hundred tools that were cheap, but died or got stagnant or let bugs fester because they couldn't afford to hire devs.
Sure, I agree; I was concerned about the pricing because the features seemed pretty limited. Some "killer" features I would love to see are editable components and themes, both of which the developers seem to be working upon. I would definitely consider buying with some improvements.
This looks great! I was thinking more on the lines of writing and adding custom components by myself. It'd help in cases which require more nuance or components like sidebars or parallax divs which the current library is missing. This is just a passing thought though.
Totally. I had been planning on moving from vanilla/jquery to a framework (Angular, React) for a long time but the initial setup and complexity always repelled me. I knew Vue.js was what I wanted the moment I read the docs.
Pros:
- Setup is pretty quick, you can move quickly from scratch.
- Deployment is painless.
Cons:
- Firestore is NoSQL which is a huge caveat.
I had to scale the project and add some features later on. Faced some bumps here and there but nothing major (since firebase is still under development). AWS also has similar offerings (lambda, hosted DB etc.) in the same space. I haven't tried them out but look forward to doing so.
For frontend use Vue 10/10 especially if you're looking to put together something quickly. I felt Vue provides a lot more room for "hacking" quick solutions(and improving on top of it later) compared to Angular or even React.
I only prefer this stack for "reactive" web apps though that have a lot of dynamic components. For a traditional website I'd still go with jQuery/Django/SQL.