Things I wish I knew about state management when I started writing React apps

Re:Things I wish I knew about state management when I starte... by flukus on Monday February 10, 2020 @05:46PM (#22294246)

> A framework that has no community support, no stackoverflow articles to help out and most likely minimal explicit documentation.

But there are gains too. The custom framework is probably much smaller and less complex, easier to know 100% of. It can be stepped through in the debugger. It's much easier to change and add features that your company needs, there's no outside bureaucracy to get in the way.

I disagree you're inventing your own framework too, there is a distinction to be made between libraries and frameworks. Just because I'm not using a framework doesn't mean I'm reinventing it, I could be using something like knockoutjs instead, or even postbacks.

[ Parent | on HN ]

Re:Things I wish I knew about state management when I starte... by spookthesunset on Monday February 10, 2020 @10:50PM (#22295886)

Mark my words, you’ll be spending the rest of your days poorly reinventing what was already done in a real framework. I’ve seen what comes of these “I don’t want to use a bloated framework” shops and it is never pretty. The second the people who eschew mainstream frameworks leave, the devs who are still are around will quickly rebuild around a real framework.

[ Parent | on HN ]

Re:Things I wish I knew about state management when I starte... by arvinsim on Monday February 10, 2020 @08:00PM (#22295054)

React, Vue and Angular can all step through debuggers.

[ Parent | on HN ]