Why don't more developers "use the platform"?
Software engineer Nolan Lawson explores why developers often choose third-party libraries over native web platform features. He argues that historical browser inconsistencies and developer familiarity with framework ecosystems drive this preference despite the performance benefits of native APIs.
Why it matters
Understanding the tension between native web standards and framework-based development is crucial for the future of web performance and browser architecture.
by Nolan Lawson in Web , software engineering .
For years, advocates for web standards, performance, and accessibility have implored web developers to “use the platform” . I’ve often been one of those advocates.
The argument is simple: why build something yourself, in JavaScript, when the browser can do it for you? Whatever you build, it’s likely to have poorer performance and worse usability than something the browser could just give you out-of-the-box.
I think it’s worth taking the other side, though, if for no other reason than to understand where the “platform-skeptic” developers are coming from. If “use the platform” is so obvious, then why do so many people seem to need convincing?
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in