On The Web, Yesterday’s Questions Are Answered in Today’s Platform APIs
Which makes him knowingly conclude in error:
I wonder if this will forever be a problem of the web? I encounter this issue all the time. For example, a question about traversing the DOM in a specific way is always answered first and foremost by a jQuery solution. That’s slowly changing (sidenote: I’m sure that’s why the word “vanilla” was invented, to help with search queries). But in 10 years, I bet a lot of our questions about building for the web (how can I encapsulate styles with my code?) will have answers tied to the popular libraries of the decade (here’s a CSS-in-JS library).
It seems platform answers will always lag behind library answers. How could it be any other way? That’s the route we’ve chosen to go on the web. That’s why XHTML died. We decided it’s better to discover new platform APIs in userland and port them back into the platform. A byproduct of that choice seems to be that we’ll always be fighting the problem described above. Which means the following:
Today’s questions are answered in today’s library APIs. Yesterday’s questions are answered in yesterday’s library APIs—and today’s platform APIs.