Framework and compiler authors still shipping code
Creators of major frameworks and build tools who are still committing to the projects they started, years or decades in.
关于此页面
网站界面已按你选择的语言显示。本页的长篇正文以英文撰写，目前尚未翻译。
| # | 开发者 | 以什么闻名 |
|---|---|---|
| 1 |
Evan You
@yyx990803
|
Created Vue.js, then built Vite, the build tool now underneath Astro, SvelteKit, and Nuxt. |
| 2 |
Rich Harris
@Rich-Harris
|
Created Rollup and Svelte while working as a graphics editor in newsrooms, not as a full-time engineer. |
| 3 |
Anthony Fu
@antfu
|
Core team on Vite and Vue, and author of UnoCSS and a long catalogue of build tooling. |
| 4 |
Ryan Dahl
@ry
|
Created Node.js, then a decade later started over with Deno, addressing his own public regrets about the first one. |
| 5 |
Taylor Otwell
@taylorotwell
|
Created Laravel and built Forge, Vapor, and Nova on top of it without ever closing off the core framework. |
| 6 |
shadcn
@shadcn
|
Built shadcn/ui around copying source into a project instead of installing a package - the React ecosystem quickly imitated it. |
Most frameworks outlive the excitement of their launch and settle into a long maintenance phase, often under a foundation or a team the original author stepped back from. The developers on this list are a counterexample: years or decades after the initial release, the commit history still runs through the same account that started it.
Starting a framework rarely looks like starting a framework
Evan You built Vue as a side project after leaving Google. Rich Harris built Rollup and Svelte while working full-time as a journalist. Ryan Dahl wrote the first version of Node in a burst of frustration with existing async I/O models. None of these began with the institutional backing that the resulting projects now have - the backing came after the tool proved itself.
Staying past the interesting part
The hard part of authoring a framework isn’t the initial design - it’s the years of compatibility decisions, deprecation cycles, and unglamorous bug triage that follow. Taylor Otwell has shipped Laravel releases for over a decade. Anthony Fu’s contribution graph is close to solid, spanning dozens of actively maintained repositories rather than one big launch followed by silence.
That sustained presence is the actual signal worth reading on a profile like this - not the size of the initial announcement, but the years of ordinary commits after it.
What this means for your own profile
A framework doesn’t need to be popular to demonstrate this pattern. What reads well on a profile is evidence that you kept showing up for a project after the first version shipped: issue responses, version bumps, and fixes for problems only real users surface.
You can see what that sustained history looks like on a showcase profile, or generate the same breakdown for your own account.