| My current preferences are Large or complex apps (such as those at work or things I intend to have a long lifetime): - Backend: Rails - Frontend: Ember The combination of these two is really powerful. I can focus on my complex problem domain and not have to make too many choices about project structure, testing setup, and other decisions that lead to bike-shedding. Smaller applications (such as side projects): - Backend: Rails, Phoenix, or Amber - Frontend: Ember, (P)react Rails & Ember are still very productive for small apps, but I'm finding Amber (written in Crystal, similar ethos to Rails) to be a faster, smaller alternative when a side-project is resource limited (plus, it's an interesting new community). Preact and React are quite good for building small things quickly or dropping into existing projects, so I've enjoyed them in that context. Ember and Rails are phenomenal over a long period of time, because they tend to have a relatively smooth upgrade path (in many cases with Ember, there are automated tools.) I'm a strong proponent of Postgres. It gets better with every version and is great for both development and production use, especially if you want to do zero-downtime deploys (Postgres has some cool tools for avoiding locking of whole tables during updates, e.g. concurrent indexing, etc.) |