>In the current landscape doing things "the hard way" in plain JS is often simpler than with React. I'm not sure what "simpler" means to you. It is extremely

>In the current landscape doing things "the hard way" in plain JS is often simpler than with React. I'm not sure what "simpler" means to you. It is extremely simple to create and deploy a framework based app; `npm create vue` give it a name, answer a few questions or accept the defaults. I find programming in such an environment very "simple", because the framework is hiding a lot of complexity. > You will give up reactivity, testability, declarative rendering, and the ability to hire any passersby, in exchange for not having to deal with a rube goldberg contraption of hooks, dependency tracking, query caches and state management, with a complex build system. All I can say is: if you have a codebase that has those issues, then the alternative implementation without a framework would be much more difficult to manage. It's true that Webpack can be very complex to configure, but out of the box configuration gets you pretty far.