The short answer: there is no single official feed of web development news, but you can build one in about twenty minutes from four kinds of source — an aggregator, a weekly email, the browser vendors' own blogs, and a feature-status tracker. If you want one page to open each morning instead, daily.dev is the closest thing to a ready-made option: a free, ad-supported personalized developer feed that pulls from outside publications and can take over your browser's new-tab page.
The reason to combine sources rather than pick one is that they fail in different directions. Aggregators are fast but noisy, newsletters are curated but weekly, and vendor blogs are authoritative but only cover their own browser. Below is what each one is actually good for, and how to merge them without paying for a reader.
Table of Contents
- The one-tab option: daily.dev
- Why a weekly email still beats a live feed
- Hacker News and Lobsters are moderated, not neutral
- Go to the vendors for anything you plan to ship
- The feed that tells you when a feature is safe to use
- Merging them into one actual feed
- Frequently Asked Questions
The one-tab option: daily.dev
daily.dev replaces your new-tab page with a feed of posts from developer publications, which means you read news as a side effect of opening the browser rather than as a task you have to remember. You follow topics and sources, and it personalizes from there. Mobile apps cover the same feed.
Be slightly careful with the catalog size. daily.dev's own documentation puts the source count at over 1,300, while its marketing copy claims 2,000+ — close enough to call it "well over a thousand sources," and not close enough to quote a number in a client report. The trade-off is the usual aggregator trade-off: breadth over judgment. You will see a lot of listicles alongside the genuinely important releases, because popularity and significance are not the same signal.
Why a weekly email still beats a live feed
If you only have fifteen minutes a week for platform news, spend it on a hand-picked newsletter rather than a firehose. Frontend Focus is a free once-weekly roundup of front-end news, articles and tutorials covering HTML, CSS, browser tech and the web platform, published by Cooper Press. It has been running for a long time under two names — it was HTML5 Weekly until the July 6, 2016 issue, when it was renamed.
The editorial filter is the product. Someone has already read the week's output and discarded most of it, which is work you would otherwise do yourself at a worse hit rate. The limitation is latency. A weekly cadence is fine for "CSS gained a feature" and useless for "a package you depend on shipped a malicious version last night." Pair it with something live.
Hacker News and Lobsters are moderated, not neutral
Both link aggregators are worth following, but treat their front pages as edited publications. Hacker News ranks submissions on a decaying score rather than raw vote count — Ken Shirriff's analysis of the ranking algorithm approximates it as upvotes^0.8 divided by (age in hours + 2)^1.8, with stories re-ranked periodically. The same analysis found roughly 20% of front-page stories carry some kind of penalty, so what you see has been shaped by moderators as well as by arithmetic. What that formula means in practice: age punishes a story much harder than votes reward it.
A post needs to accumulate attention fast or it never surfaces at all, which quietly favours provocative framing over slow, detailed technical writing. Lobsters is the narrower, calmer alternative — an open-source, computing-focused link and discussion site. It is also invitation-only: a new account needs an invite from an existing member, invites are public in a visible invite tree, and an inviter loses standing if their invitees behave badly. That accountability is why the volume stays low and the comments stay technical. It also means you can read it immediately but cannot post until someone vouches for you.
Go to the vendors for anything you plan to ship
Aggregator coverage of a browser release is a summary of a summary. The primary sources are short and worth reading directly:.
- **Chrome** — the Chrome for Developers blog publishes an official RSS 2.0 feed at developer.chrome.com/blog/feed.xml, mirrored at /static/blog/feed.xml, with an index of per-section feeds listing the rest. Note that the blog feed vanished in January 2024 and the feeds page was Google's replacement, so expect these URLs to move again and check the index if one breaks.
- **Safari** — WebKit posts a per-release feature write-up for every Safari update, which is the main channel for Apple-side platform news. The scale is real: Safari 26.0 shipped 75 new features, 3 deprecations and 171 other improvements; 26.2 added 62 features; 26.4 added 44 features and 191 bug fixes, including the Keyboard Lock API.
- **MDN** — the MDN Blog has run since May 2023 at roughly two to four posts a month and offers an RSS feed. Its newest entry is "Introducing the MDN MCP server," published by the MDN Team on June 15, 2026. It also carries clearly labeled sponsored posts from companies including DebugBear, Vultr and GitLab — labeled is good, but read those as vendor content.
The feed that tells you when a feature is safe to use
News tells you a feature exists. It rarely tells you whether you can ship it, and that gap is where the Web Platform Status dashboard at webstatus.dev earns its place. It tracks over 1,000 web platform features — close to 100% coverage — from the W3C WebDX Community Group's web-features project, and since mid-2026 you can sign in with GitHub to get notified when a feature reaches Baseline Newly available or Widely available.
Those two labels are the vocabulary the rest of these feeds now use, and the distance between them is larger than most readers assume. Per Google's Baseline documentation, a feature becomes "Newly available" once it is supported across the core browsers, and "Widely available" only 30 months after that interoperability date. So the practical reading of any excited post about a new CSS or JavaScript capability is: it works in current browsers, and it is roughly two and a half years from being safe to ship unconditionally to a general audience. Until then you need a fallback or a progressive-enhancement path.
Merging them into one actual feed
Every source above except daily.dev and Hacker News comments exposes RSS, so a reader can collapse them into a single list. Feedly is the common choice, and the free tier is tighter than it looks: a 2026 pricing breakdown from Readless puts the free plan at 100 sources in 3 folders, Pro at roughly $6–$6.99 a month for 1,000 sources, and Pro+ at about $8.25–$12.99 a month.
That summary notes sources disagree on whether the "3" limit counts folders or feeds, and on whether the free tier shows ads — so confirm the current terms on Feedly's own pricing page before you commit. A minimal setup that stays inside any free tier: Three folders, well under 100 sources, and no subscription. Add daily.dev as the new-tab page if you want serendipity on top — just keep the vendor folder as the thing you check before writing a line of production code, because that is the only set of sources that speaks for the browsers themselves.
- One folder for platform releases: Chrome blog feed, WebKit, MDN Blog.
- One folder for curated weekly reading: Frontend Focus and one or two peers.
- One folder for discussion: Lobsters' RSS and a Hacker News front-page feed.
- Baseline notifications handled outside the reader, via a webstatus.dev GitHub sign-in, so shipping decisions arrive as alerts rather than as items you might scroll past.
Frequently Asked Questions
Is a free Feedly plan really enough for this?
Yes for a focused setup. The free plan allows 100 sources in 3 folders per the Readless pricing breakdown, and a working web-dev setup needs perhaps a dozen feeds; paid tiers matter when you track hundreds of company blogs or need search across archives.
Why can't I just read Hacker News?
Because its ranking actively decays age — upvotes^0.8 over (hours + 2)^1.8 — so slow-burning technical writing often never reaches the front page, and about 20% of front-page stories carry a moderation penalty. It is a good discovery channel and a poor record of what shipped.
Which single source should I add if I only add one?
webstatus.dev. The other feeds tell you a feature exists; it tells you when the feature crosses into Baseline Newly available or Widely available, which is the only question that changes what you write.




