Tracking JavaScript Pioneer Contributions Over Time
When I first started paying attention to who actually built the tools we use every day, I noticed there was no coherent timeline. Everyone referenced different dates, different milestones, different people. Some credited Brendan Eich with everything from 1995 onward. Others pointed to Tim O'Reilly, Douglas Crockford, or Ryan Dahl depending on which ecosystem they came from. The problem wasn't that the information didn't exist. It was scattered across GitHub release pages, old Usenet posts, conference videos from 2009, and blog posts that had rotted behind paywalls. So I built something to put it all in one place. Not a fancy dashboard. Just a chronological chart showing when key JavaScript figures published their first significant work, released their first major library, or gave the talk that shifted how people thought about the language. I've been maintaining this for about three years now, and the process is straightforward if you know where to look.
The When Of Js Mothers Day Charting The Exact Date Of A JavaScript Pioneers Recognition
The concept here is simple: map individual contributors to specific dates, then sort them along a timeline. The "Mothers Day" part isn't literal. It's a reference to the original project name from 2018 when someone tried to map JS pioneers to their mothers' birthdates as a quirky attribution method. That approach fell apart fast because people didn't know their mothers' birthdates and the data was meaningless. The modern version just charts exact recognition dates - when someone's contribution first became publicly visible or formally acknowledged. Here's how I do it now. First, I pull raw data from three sources. GitHub's earliest commits for each author. The Internet Archive's Wayback Machine for blog posts and announcement pages. And npm's publish timestamps for library releases. I cross-reference all three. If GitHub shows a commit from March 2014 but npm shows the package published January 2013, I use the npm date as the primary recognition point and note the discrepancy. I keep a spreadsheet. Columns for name, primary contribution, earliest verifiable date, source URL, and a confidence rating. Confidence matters because some dates are uncertain. I mark them as low, medium, or high. Low confidence entries get flagged with a question mark. High confidence ones have multiple sources confirming the same date.
Once the data is clean, I push it into a simple D3 timeline visualization. Nothing elaborate. Just nodes on a horizontal axis labeled by year, with hover states showing the person's name, their contribution, and the source links. I host it on a static page because there's no reason to run a server for this. The chart updates whenever I add new entries, which happens when I find a missed contributor or correct a date. The hardest part isn't the coding. It's the verification. I spent two weeks in 2022 chasing down whether Node.js actually shipped with npm bundled in version 0.5.0 or 0.6.0. The npm publish date said one thing. The Node.js changelog said another. The original announcement blog post was gone. I ended up pulling the actual git tags from both repositories and comparing their dates. Node v0.5.0 was tagged October 27, 2011. npm 1.0.0 was tagged October 28, 2011. They shipped separately. Everything online had been wrong about this for years because someone misread a Reddit thread in 2013 and everyone copy-pasted the error. That's the real issue with this kind of charting. The JavaScript ecosystem runs on inherited misinformation. A single wrong date gets repeated across dozens of articles, conference slides, and Wikipedia pages until it becomes accepted truth. My job is mostly catching those errors before they compound further.
Get the Full Details
Another problem worth noting: the chart inherently favors people who document their work publicly. Contributors who worked in corporate environments, or who published through proprietary channels, or who simply didn't keep records, are underrepresented. The timeline will always be incomplete. I add a note about this on the page itself. It's not a flaw in the tool. It's a limitation of the available historical record. If you want to build something similar, start with a narrow scope. Don't try to cover every JavaScript contributor. Pick a category - say, tooling authors from 2010 to 2015. Verify each date before adding it. Document your sources visibly. And assume everything you find online is wrong until you confirm it yourself. The full dataset and chart are available at the project repository. I update it monthly when I have time. There's an open issue tracker for corrections. If you spot an error, open a pull request with evidence. I review them slowly but I do read every one.
