|
|
|
|
|
by git-pull
2516 days ago
|
|
The stack I suggested is opinionated for an MVP. I won't defend something so specific to my personal case. However there's more than that at play. Let's just assume bootstrapping the basics, with a requirement there's a backend and it has to be deployed: 1. If there's a requirement to have a backend connection and deploy the mvp, that rules out create-react-app / @vue/cli in most cases since it'd be too custom. The app would need to be ejected. But even further, the ejected app is overengineered. The byproduct of create-react-app's ejected output is so bad I wrote https://github.com/tony/react-typescript-vanilla-starter, https://github.com/tony/vue-typescript-vanilla-starter simply for the sake of getting a minimalist webpack+typescript+hotreload+prod build config working. I found it challenging to patch together webpack + ts + react/vue from scratch. 2. Going to a stack outside of our usual stack takes time to relearn. Not necessarily a bad thing, but people are going to be rusty. |
|