3 ms·
Salient quote: > To pick a specific example: the problem with an over-engineered form is that the amount of code required to replace no engineering (i.e. nativ
by nathan_long 9y ago
Salient quote:
> To pick a specific example: the problem with an over-engineered form is that the amount of code required to replace no engineering (i.e. native form controls with basic styling) is enormous and almost always only partially successful (i.e. under-engineered).
> They are under-engineered because they are over-engineered—tried to replace native controls.
> This is the basic argument against most forms of website over-engineering: scroll-jacking, manipulating history with pushState, completely customised form controls, etc.
> Recreating browser features will almost always be both under- and over-engineered.
- tboyd47 9y agoThe worst thing about reimplementing native controls (and what everyone misses) is that those native controls don't go away. Instead, their behavior becomes undefined as the system grows around the reimplementation.