Building a web app with no framework
I think we should find a balance between on using frameworks. Here&#x27;s my experience with mobile, but the same idea applies:<p>In my early years (circa 2015) I didn&#x27;t know much about patterns and wrote this &quot;super smart&quot; code where I called all the API calls yet never used the results directly, passes all the responses through a pipeline, wrote them into a flat normalized state, then fired change events, and my views actually listened to change events and reacted to them to update the UI with a single-source-of-truth local store in both Objective-C and Java for our iOS and Android apps. (There were other &quot;weird&quot; things that &quot;I invented&quot; but this was the relevant part)<p>Sounds familiar? Then, years later, I learned about React Native and redux, and saga, which (albeit with a completely different language and syntax) roughly worked the same way I envisioned and wrote my app (which worked flawless and bug-free by the way, a validation of the pattern works).<p>Now, I use React Native (which also came as a bonus because when I learned it I also have automatically learned its web-counterpart React.js as well) which has the same &quot;vision&quot; in terms of store and observing&#x2F;reactiveness.<p>Now I use React [Native] because it gets my work easier, faster, and is super popular. I know it will probably not be super popular in, say, 15 years, but the ideas and patterns (reactive programming, state&#x2F;reducers etc) will be here, and I can adapt to $(popular-reactive-framework-with-nice-syntax-of-year-2035) because that will be making my job easier. (Assuming that I&#x27;ll still be doing mobile&#x2F;web development)<p>I think as long as we want to get the general philosophy of these frameworks and know how to implement the parts needed from scratch if we ever need to, they do more good than harm.