[hobonumber1]

Focus on the product, not the technology used to build it. If your tech decisions (vanilla Redux) makes you productive, then use that. Otherwise, you'll be stuck in a never-ending loop of upgrading your stack all the time.

[arcticfox]

I just downgraded my stack because state of the art kept breaking too much and slowing me down big time. Comfortably a step behind the cutting edge now and it feels great. Credit to Dan Abramov (creator of Redux) for writing "You Might Not Need Redux" and showing me the light... I needed just about nothing on his list of why Redux can be a critical help.

[AtheistOfFail]

Remember when Rails + JQuery + HTML + CSS just worked and you didn't have to deal with thousands of fucking JS dependencies just to render a single page. Yeah, I do too.

[moron4hire]

Wait, you're not seriously going to bring up Ruby on Rails and try to say something about not having to deal with thousands of dependencies?

[AtheistOfFail]

Yes, but Ruby on Rails dependencies aren't a fucking headache to manage.

I've only had one issue with Rails dependencies. They work fucking great if you just want to drop them and leave in the default configuration but the moment you try to customize them... holy shit balls.

[dabockster]

Remember when server side rendering plus some Nginx load balancing/port forwarding was all that was needed to show off to other technologists?