January 19, 2026
No JS, No AI, All Drama
Show HN: GitClassic.com, GitHub circa 2015 without JS & AI
GitClassic brings back 2015 GitHub; fans cheer, bugs crash the party
TLDR: GitClassic rebuilds GitHub like it’s 2015—no JavaScript, no AI, super fast—and it’s already drawing curious users. The crowd loves the speed and simplicity but clashes over bugs, rate limits, and missing pull‑request tools, while the creator lures testers with a half‑price Pro offer for private repos.
The internet is reliving 2015 and arguing about it. New site GitClassic promises no JavaScript, no AI fluff, and lightning‑fast pages so your laptop fan doesn’t scream just to read a README. It’s old‑school GitHub vibes: clean, quick, and just code. Early traffic popped (13.2k pages in a day), and the creator even dropped a 50% off code (HACKERNEWS) for Pro to view private repos.
But the comment section? Spicy. One power user swore they’d pay now if it supported full issues and “PRs” (pull requests) with review/merge—aka a real replacement for modern GitHub’s slow, clicky maze. Others hit the brakes with live bug receipts: “repos.filter is not a function” on pixijs and rate‑limit smackdowns on navidrome. Cue the split: Team Nostalgia chanting “bring back the fast web,” vs. Team Reality pointing out error pages and API walls.
Design wars erupted too: which 2015 look to revive—and yes, dark theme, please. People joked that it’s “GitHub without the 47MB” and cheered the “no AI garbage” stance, while poking fun that the trending list still features AI‑named repos. It’s scrappy, it’s fast, it’s broken in places—and the crowd can’t look away.
Key Points
- •GitClassic.com provides a GitHub-like interface modeled after the 2015 era.
- •The site uses zero JavaScript and serves server-rendered HTML pages.
- •AI features such as Copilot prompts and AI summaries are intentionally excluded.
- •Pages are roughly ~10KB, with Feed/Explore views and trending repositories available.
- •A Pro plan costs $40/year and enables access to private repositories; feedback is collected for feature requests like contribution graphs.