3 ms·
> Browser vendors responded to the JavaScript renaissance by adding new APIs, many of which conflicted with Prototype’s implementation. And developers began to
by karmakaze 7y ago
> Browser vendors responded to the JavaScript renaissance by adding new APIs, many of which conflicted with Prototype’s implementation. And developers began to show a preference for small, self-contained, modular libraries over more monolithic frameworks.
I also find this very interesting. Many codebases decline in usage by not being actively developed. Other times, changing the way things are done goes against the core and is better off leaving it alone, and developing anew. Of course this is only clearly visible in retrospect. I'm generally against adapting to trends and wonder why perfectly complete and functioning frameworks need to be actively developed. This is why--we want to know that the framework will change with the users.
The second part of the trend to prefer modular libraries, I think was transitional as there was no one framework that had the best of breed components and using individual libraries produced a better ad-hoc framework. Now we have something in-between with coherent frameworks but still having replaceable parts.