3 ms·
nope. I'm done. There are enough JS frameworks, client and server side. I don't need to look at another one. I'd really like 2016 to be the year that everyone
by marcus_holmes 11y ago
nope. I'm done. There are enough JS frameworks, client and server side. I don't need to look at another one.
I'd really like 2016 to be the year that everyone who thought of making another new JS framework decided to not do that and instead go fix bugs in one of the existing ones that people are already using.
- dplgk 11y agoWhat do you like to use?
- marcus_holmes 11y agoReact+Redux and Express at the moment, but that's at the end of a long, long trail of trying out JS frameworks. I got fed up of constantly learning new frameworks searching for that One True Framework that would be expressive and powerful but without too much boilerplate and... well, you know the quest. I gave up looking for the Holy Grail and settled on what seemed to be working for me at that point (like quite a few other devs I know). It just got too much, the constantly learning new apis in order to keep up. hence "I'm done"... I'm going to go deep instead and really learn how to use a single environment properly, as in 10,000 hours properly.