3 ms·
You don't need a route library. You don't need a form library. What do you need a routing library for? Have a single controller component (usually the most out
by debaserab2 9y ago
You don't need a route library. You don't need a form library.
What do you need a routing library for? Have a single controller component (usually the most outer shell app component) and sprinkle in further functionality (e.g. history pushState) as necessary. Don't build it out until you actually need it.
I've never needed a "form library" because forms are almost always interactive in some specific way. Using a form library is almost always guaranteed to just get in the way.
You don't need to have a global state management library either if you have a good grasp of your apps data structures and how they need to be passed into components.
I find with React I get the opposite of javascript fatigue: it's so easy to build anything you need once you understand react that you won't need to search for all those libraries and code snippets.
- oulu2006 9y agoI guess we have completely different approaches to software development. I really hate reinventing the wheel, especially when good quality production tested solutions are out there. React libraries, quality wise, I've found hit or miss. I find Vuex a very nice global store and the tooling (chrome plugin etc..) is top-notch.
- debaserab2 9y agoYou won't be reinventing the wheel for things like global state management and javascript routers. I promise. These libraries are huge solutions to problems that may or may not be huge - and in most of the cases I've seen, YAGNI. The concept of maintaining application state is nothing specific to SPA's. What is new is the idea that every application must have a global data store where all state is saved. This is a trend and not always necessarily a best practice. This isn't a matter of reinventing the wheel, it's a matter of using an oversized solution for an undersized problem.