Why don't more developers “use the platform”?
- ID
- 31643
- Status
- summarized
- Published
- 04 Oct 2026, 12:10 PM
- Fetched
- 04 Oct 2026, 11:21 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://nolanlawson.com/2026/10/03/why-dont-more-developers-use-the-platform/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.5
- Created
- 04 Oct 2026, 11:21 PM
- Tags
- Audience
- developersvibe_coders
What happened
Nolan Lawson's October 3, 2026 post on Read the Tea Leaves takes the platform-skeptic side of the 'use the platform' debate, giving three reasons developers still reach for libraries instead of browser APIs: browsers spent years behind the ecosystem (jQuery filling gaps while IE6 aged out), developers search npm and React components out of habit even when a standard exists, and web platform documentation was scattered across StackOverflow, CSS Tricks and blogs until MDN became the default reference (with web.dev as Google's more future-facing arm). He notes most browsers are now evergreen — Safari is 'debatable, although ~7 times per year ain't bad' — which undercuts the original justification for rolling your own. The Hacker News thread drew 203 points and 189 comments, and the excerpt cuts off mid-sentence, so the piece's later arguments aren't visible here.
Why it matters
This is a framing essay, not a benchmark or a shipped change — nothing here forces a code change, so treat it as a prompt to check one dependency you added by reflex. The concrete lever is that the historical excuse (browser lag, IE6) is largely gone while the npm reflex and doc fragmentation are not, so the decision should be per-feature: ask whether a baseline standard already covers it before adding a package. Safari's roughly 7 releases per year is the one number worth carrying into your baseline targets if you still support it.
Discussion angle
Pick one component your team pulled from npm in the past year and check whether the platform now covers it (CSS position: sticky is the article's own example) — then argue live whether the real blocker is the browser's remaining gaps or the team's habit of searching npm first.