So, with 2 commands you can have a CRUD website with all the values you need.
Really easy, really flexible.
[0] - https://symfony.com/doc/current/controller.html#generating-c... [1] - https://symfony.com/doc/current/doctrine.html#creating-an-en...
Tables, Lists and Forms are all built-in and nicely abstracted, along with an Auth system. It's built using react and redux which makes it easily extensible. And there's plenty of database connectors for it too.
Framework7 hybrid front end + Parse Server back end, hosted on Heroku and mLab.
Or if you want lighter and simpler, with less scalability, jQuery + Bootstrap + Parse Server. Maybe Vue.
Setting up Parse Server is poorly documented, so I wrote a little walkthrough: https://medium.com/@smuzani/setting-up-a-mobile-backend-serv...
I'm not sure about the others, but I'd say it would take about 2 hours to build a quick listing app with little experience.
[1] https://github.com/mikro-orm/mikro-orm
(Note: v3 is beta and what you should start with. Quite stable as it has 100% coverage.)
They claim it is very fast development once you get past some comfort level. There is a bit of jump involved when it just clicks. I've tried a few times and it seems like slugging it out with a lot of magic.
While I write and like Python more than PHP, something like Laravel or Symfony seems more logical for CRUD than Django to me.
The real problem, I think, is that 95% of real business problems are not simple CRUD apps. There is always some complication unique to your domain that burdens you with constraints. Also, it seems like authentication is a problem that is still not solved smoothly without paying for SaaS. It doesn’t take long before you feel like you’re anything but a standard “CRUD app.”
My lesson from the past few years has been this: stay within the guardrails as much as possible. Use frameworks when you can, and try not to deviate too far from their conventions, no matter how tempting. If you stay within these rails, it’s fairly easy to ride the flow of changes and keep your code up to date without losing velocity on new features.
Whatever you choose, you're still going to be using it in three years. The safest option is probably to pick something really popular.
The best part is you retain complete freedom and control to manage any part of the process both on the client and server side and "hook" in practically anything else on top of it.
Even in Meteor there are new ways but require more learning.
[Django](https://www.djangoproject.com/) is also very good if you like Python.
IMHO, the best part of both is that you don't need to worry about a TON of standard functionalities like authentication, logging, messaging, security (to a good extent), user management, etc.
I program on the side and focus more on the business, and just find comfort in JS although I do analytical work in Python (and integrate them using hacks and bridges .... works fine for most part ... little slow and clunky but works and saves a lot of dev time)
> most flexible
Pick one.