Readit NewsSo when you're actively maintaining something and you bring in a dependency, you're in some sense outsourcing some of that work, whether it's a colleague or an outside party maintaining that library. The specifics of who begins to matter. Is it the React team maintaining that part of the codebase? Is it lonely author in Kyiv? Or is it you?
So what is it like to be the colleague of someone who wrote their own Tanstack Forms and successfully or unsuccessfully integrated with Zod and the like? Or did they choose to write their own runtime type validator too? That's maintenance burden.
Cases in which this can happen. - I orient myself before overtaking another car on the highway or motorway. - I position my hand wrong on the steering wheel and the camera can no longer see me. - I put on sunglasses when I am driving against a low sun.
It can be turned off, but if you live in the EU it is required to enable itself once the car has been turned off/on.
It will also happily warn me if it thinks I am speeding based on errornous gps data. This feature also turns itself back on once the car has been turned off.
Otherwise vanilla forms are great in React. If you did this by hand in Vue or vanilla it would also be hell.
Also in terms of maintenance burden the top libraries in this space are massively popular. Most here would likely be making a great maintenance burden decision in offloading to well reputed teams and processes rather than in housing your own form and validation library.
It's really not. If you walk away from your project for 7 years, your vanilla JS will just load into the web browser and still behave the same. If you walk away from your React (or other NPM-based project) for the same amount of time, you won't be able to build all your dependencies from source without spending time updating everything. Going with something like HTMX or plain JS vastly reduces your maintenance overhead.
Are there any serious objections to that line of reasoning?