HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
extensibleweb
manifesto
Web Development2013–2025
extensibleweb / manifesto

manifesto

The Extensible Web Manifesto

10Distinct people
19Mentions
0Explicit recommenders
335GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Extensible Web Manifesto

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year19 dated mentions

Observed mentions: 2013-06-10 23:19:11 UTC to 2025-09-15 21:03:13 UTC.

01232013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC110
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

What Hacker News says

3 sources
> Browsers are massive, complex, and resource hungry. Sure, I'll just run my application inside another complex application inside a complex OS. What's another layer? But actually, raw JS, HTML, and CSS are too slow to work with, so I'll add another layer and do it with React. That's just your opinion, and you're overgeneralizing one framework as the only way. A 2009 mobile phone did pretty damned awesome with the web. The web is quite fast if you use it well. Sites like GitHub and YouTube use web components & can be extremely fast & featureful. Folks complain about layers of web tech but what's available out of box is incredible. And it's a strength not a weakness that there are many many ways to do webdev, that we have good options & keep refining or making new attempts. The web keeps enduring, having strong fundamentals that allow iter
Read the rest
ation & exploration. The Extensible Web Manifesto is alive and well, is the cornerstone supporting many different keystone styles of development. https://github.com/extensibleweb/manifesto It's just your opinion again and again that the web so bad and ke, all without evidence. It's dirty shitty heresay. Native OSes are massive, complex, and resource hungry and better replaced by the universal hypermedia. We should get rid of the extra layers of non-web that don't help, that are complex and bloated.
In WASM Is the New CGI
Ah yes, another web-grumbler, here to tell us to abandon the connected platform available on all devices that is hugely successful. It's just your opinion that the web isn't great for UI. It doesn't have much evidence (and you certainly aren't making any testable assertions). If the web was so bad you'd think native apps would be ruling the planet, would be vastly more popular & loved & be what everyone is trying to ship. But that's not the case. The web is everywhere and companies have full faith in the web and it's working. > But the web isn't great for building input UX (it's all bloat + jank and you have to completely reimplement the input elements to do anything useful, on top of shifting sand) Theres a school of thought that wants a complete & total solution, handed to them, that does everything, that everyone uses. These people are
Read the rest
ideologically going to hate the web. Even though there are countless really really good well made component libraries out there, the fact that it's not all baked in upsets a certain type a lot. But, this is the strength of the web. The web is free to shift & change & emerge new patterns & ideas, is free to have new and different components emerge. This is a strength, this is why the ecosystem keeps steamrolling everyone else: everyone else is singular & tries to be complete, and the web is legion & perpetually innovating on the edge in a way classic platforms never can. Some people see weakness, but the ideas of the low level Web Extensibility Manifesto keep the web buoyant & iterating for developer and user happiness in ways no other system has remotely been able to achieve. https://github.com/extensibleweb/manifesto The other good news is that the OpenUI community group got formed & is upstreaming into HTML more components. Popovers and dialogs are both about to be fully usable by anyone. There's a ton of drive to improve the core elements available on the web. While also not harming that extensibility. https://open-ui.org/ > the data can be shared or backed up somehow sure; that's just file hosting with a collaboration layer maybe. Being connected software is the new base expectation, is table stakes. You have to have connected software to succeed. And the desktop doesn't have this. It's all special snowflake systems, all build it yourself. It's the default for software to be connected on the web. And on the web it's the default that it'll run on you desktop, your phone, your tv, your fridge, and all your neighbors friends and coworkers device. For something like a notion clone here, I think most users would have an enormous enormous expectation that this kind of groupware be on the web. Trying to reinvent a collaborative knowledge capture paradigm on desktop sounds absurd & sounds like folly. The desktop has no starting place for developers nor users. When I think of performance specifically, I think of how much opportunity the web has. Any popular software platform is going to have an absolutely gobsmackingly huge amount of really bad software written for it. And that challenge is magnified greatly in the connected age where vastly more data lives outside of your computer than on it, where your computer is at best a local cache. We will always be beset by unideal software, by bad architectures, by poor data remoting practices. But that doesn't make me sad or want to go run away to the many different native platforms, to go trip over all the same data syncing & data architecture problems there. It makes me excited to see us iterate and improve, makes me so happy there are brave people cranking out Svelte and Stencil and Lit, makes me happy we are moving forward speccing out signals and observables (although having two similar but different async data constructs maybe is a misfire, IMHO), makes me happy we are getting wasm and still so early but wading slowly off the main thread and into workers. There's so much opportunity here to iterate & improve & grow, even with what we have, and there's been such strong help & improvement ongoinglg given to the platform layer from such a wide coalition of spec authors and passionate wicg.io community members. World wide web on & on.
In Install Docmost – open-source Notion Clone
I don't see why Origin Private File System needs some fully virtualized nonsense. You can just create some fuck off far out directory for the site for this cause. Should be fine. There's already pretty safe secure & altogether sensible options for giving websites access to files. Alas it's all via even slower even worse abominations that File Access Handles, because spec authors swear it would be hell on earth if they didn't quintuple buffer every read or write, will swear we could never ever trust devs to ever possibly do a good thing. There's been such a constant hedging that being slow & adding layers of safety to io is necessary and it's taken literally decades to get even these crap ass concessions. I know this is impolite and I'm sorry but what cowardice, what unrelenting sad clutching of pearls. What utter betrayal of Extensibile W
Read the rest
In How we sped up Notion in the browser with WASM SQLite

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.