[samspot]

There are a lot of factors that make a framework either worth it or not. Here are some that lean towards framework.

* Is it an application (google docs?), if not, you may not need a framework.

* How large is the team? For a solo project, a framework offers less of a consistency benefit. In a group, having people implement the same way can be important, and a framework helps a lot.

* Are you managing a lot of application state in javascript?

I'm out of time, but those are some of the big ones. I've used frameworks in the past, but we're currently doing a classic wizard-style application, and the frameworks don't offer us a lot. If it was less site & more application, I would be pushing for one of the popular frameworks to help manage complexity. Frameworks bring additional complexity, and they need to mitigate a certain amount of complexity to be worth it.

[curiously]

im also building a wizard style app. I do feel like react could help but the work it takes to reimplement it seems unprofitable.