3 ms·
Sometimes that latest trendy framework actually is a much better approach. Wanna know how you can tell the difference? Experience. I used React for the first t
by williamcotton 12y ago
Sometimes that latest trendy framework actually is a much better approach. Wanna know how you can tell the difference? Experience.
I used React for the first time when I started building the first version of our MVP because I was familiar with and frustrated with every other front-end approach in Javascript. Angular and Ember were bulky and slow. jQuery and vanilla JS are god damned nightmares for complex interactive applications. Because I have been writing rich client applications in Javascript for the better part of a decade I could very easily assess the pros and cons of React and realize just how great of a tool it was. The same goes for why I use Browserify and why I still use Make (and not grunt or gulp, yuk) for my builds.
The database I went with? Postgres. Redis is the only NoSQL tool in my belt and I use it as basically a sophisticated caching layer, although now that Postgres has such great support for JSON documents I might be fine without it.
I know for sure that there will be new tools in the future. Most will be new versions of an old approach but implemented poorly. A few will be much better and will have a major increase in productivity.