HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
blueboxd
chromium-legacy
C++2021–2025
blueboxd / chromium-legacy

chromium-legacy

Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+

2Distinct people
22Mentions
0Explicit recommenders
451GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM 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 year22 dated mentions

Observed mentions: 2021-02-05 18:00:33 UTC to 2025-08-21 16:25:09 UTC.

02462021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 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
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC707
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC716
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC312
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

7 sources
It's not just banks. Google Maps will refuse to work if you're running OS X Lion, even if you're using a fully up-to-date version of Chromium[1] which is just as capable as any other Chromium-based browser on any other operating system. Google Maps work perfectly on Lion if you fake the user agent, because of course it does, it's a web app and the underlying OS is irrelevant. 1: https://github.com/blueboxd/chromium-legacy
In Why not to whitelist operating system user agents
I use 10.9 because out of all the OS's I've ever used, I like 10.9 the most by far, and I consider that worth the security risks. I browse the web in an up-to-date version of Chromium[0], I keep my computer behind an up-to-date router, and I trust my local software. An experienced hacker who wants to spend a few days getting into my computer will succeed, but they'd probably succeed anyway, and that's why I take measures like keeping backups in cold storage. This was the first time I've actually backported a security fix. Apple Mail is easily where I'm most vulnerable, because it's not merely an outdated app which opens untrusted content—it opens untrusted content which anyone can push to me! 0: https://github.com/blueboxd/chromium-legacy
In Zero click vulnerability in Apple’s macOS Mail
About six months ago, I stumbled across a Github repository with zero stars, called Chromium Legacy (https://github.com/blueboxd/chromium-legacy). A seemingly-unknown Github account, with no profile and no other notable projects, had single-handedly backported Chromium Canary to work on very old versions of OS X, alongside an automated build system to keep everything up-to-date. Due to my interests, I was delighted! The port had some major bugs, but I opened Github issues, and one by one, the developer fixed them. In a couple of cases, I helped track down the offending code, but he's done the vast majority of the work. At this point, I have definitely opened more issues on Chromium Legacy than anyone else. I opened two more just hours ago, and I was going to open a third... but then I didn't, because I was feeling guilty. He's always than
Read the rest
kful for the reports, but he usually apologizes (!), which makes me worry I'm just creating all this work for him... so I don't quite know what to do.
In It Doesn't Work
> Two usable browsers in Snow Leopard are: Firefox 45.9.0ESR, Opera 25.0.1614.71 Ew, no, don't do that! Use InterWeb, which is compatible with many more websites, and gets security updates. https://randommacstuff.blogspot.com/p/interweb-browser.html On 10.7 – 10.9, you can actually use a branch of Chromium. It's unofficial, but completely up-to-date, and will work with every site. It's my daily driver. https://github.com/blueboxd/chromium-legacy
In A Retrospective Look at Mac OS X Snow Leopard
A lot of people here are criticizing the methodology. That's fair, I don't know enough to weigh in. But what I can say for sure is that in real-world use, on Mac, Safari absolutely feels lighter weight than other browsers. The fans spin up less, the battery lasts 30% longer, and other apps seem to be more responsive. I don't know if that's memory or cpu or what have you, but it's real. You do pay a price in actual page-load times. Chrome absolutely has a small but noticeable edge in raw browsing speed. I suspect this comes largely from Safari's tight integration with the rest of macOS. I recently had occasion to read a bit of Chromium's Cocoa UI code (to help the developer of https://github.com/blueboxd/chromium-legacy track down some bugs), and my very surface-level interpretation of what I saw could be summed up as "how can we get rid o
Read the rest
f macOS's native functionality and use our cross-platform stuff instead?"
In Browsers eating RAM
I actually switched to Chromium as my main browser a few days ago. I'm using this branch[1], which follows upstream except for a handful of patches to retain support for older versions of OS X, which I prefer. I was somewhat surprised to see that all the syncing features seem to still exist in this close-to-stock Chromium. It encourages you to sign into a Google account to sync data, use and to use Google for search suggestions, and to install extensions from the Chrome Web Store. Does anyone know how that's possible? I'd actually be quite pleased if all of this stuff just got stripped out of Chromium. As it is, I spent quite a bit of time going through and turning off as much of it as I could, in some places via semi-confusing defaults write commands. 1: https://github.com/blueboxd/chromium-legacy
In The endless browser wars

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.