2 ms·
> Frameworks manage component lifecycle in a way the browser by itself doesn't. Which raises the question, what the heck has browser been doing after all these
by est 5y ago
> Frameworks manage component lifecycle in a way the browser by itself doesn't.
Which raises the question, what the heck has browser been doing after all these years? To replace jQuery we now have querySelector, but what's preventing browser's native support of "component lifecycle"?
- ryanbrunner 5y agoAnytime you have multiple independent companies who are competitive with each other collaborating on a shared standard, progress is going to be slow. This is especially exacerbated in web browsers when a participant with a large market share intentionally stalls progress for competitive reasons (Safari, when web browser functionality gets too close to native apps).