Bryce Wray
brycewray.com · Personal blog · on HN since 2019
Bryce Wray writes about web development, static site tools, CSS, browser market share and privacy issues like Google Fonts.
What HN saysHN commenters cite his Firefox market share post and his Google Fonts privacy article, and one links his take on feed readers.
16HN people shared it
9linked it in comments
33stories submitted
293story points
7 months agolast shared
2019people per year2026
Most-shared posts
- 1Firefox on the Brink?5 people · 11 points · first shared 2023 · discussion on HN
- 2Google fonts privacy4 people · first shared 2020
- 3From Pages to Workers (Again)2 people · 1 points · first shared 2025 · discussion on HN
- 4Astro and the Move to MDX2 people · 1 points · first shared 2022 · discussion on HN
- 5Tailwind CSS v3.2: revisiting my “feature creep” warning1 people · 110 points · first shared 2022 · 133 comments on HN
- 6How to make “localhost” slightly less local1 people · 48 points · first shared 2022 · 44 comments on HN
- 7Speaking Up for Sass (2021)1 people · 43 points · first shared 2022 · 23 comments on HN
- 8Some of the future is now for CSS1 people · 29 points · first shared 2023 · 3 comments on HN
- 9Hugo's New CSS Powers1 people · 11 points · first shared 2026 · 2 comments on HN
- 10Why I’m staying with Hugo An “interesting” learning experience1 people · 3 points · first shared 2019 · discussion on HN
- 11Beta-Testing Cloudflare Pages1 people · 3 points · first shared 2021 · discussion on HN
- 12A better way to analyze Web sites1 people · 3 points · first shared 2020 · discussion on HN
- 13Really Getting Started with Hugo1 people · 3 points · first shared 2022 · 4 comments on HN
- 14Get good Git info from Hugo1 people · 2 points · first shared 2022 · discussion on HN
- 15Static Mastodon toots in Hugo1 people · 2 points · first shared 2022 · discussion on HN
What HN people wrote when they linked it
brycewray · 2022-10-02
Possibly some perspective on why NNW gets so much love vs. News Explorer:
https://www.brycewray.com/posts/2022/04/gems-in-rough-17/#feed-readers…
wbobeirne · 2025-03-03
The article really should be "Everything Is Chrome + Safari", the "Firefox on the brink?"[1] article even shows that Safari has ~37% market share (Although the underlying site[2] currently shows me ~34%.)
[1] https://www.brycewray.com/posts/2023/11/firefox-brink/ [2] https://analytics.usa.gov/
rdlw · 2024-01-05
The US government: https://www.brycewray.com/posts/2023/11/firefox-brink/
egberts1 · 2023-12-06
And once Firefox falls below 2%, then the web developer pool for Firefox web browser will start to shrink dramatically.
Given the newest but seemingly inert MF board makeup and their lack of zeal to shore up this Firefox market share, it looks to be a certain lost cause.
https://www.brycewray.com/posts/2023/11/firefox-brink/
gigel82 · 2022-10-22
Here's Google's 1st hit for "Google Fonts privacy", you can find more: https://www.brycewray.com/posts/2020/08/google-fonts-privacy/
lioeters · 2022-10-22
My heart sank a bit when reading the phrase, "absolutely massive amount of new stuff" in Tailwind's release note. I agree with the article that this may be the inflection point where I return to just using Sass. (So far I've been using both.)
But Sass has been recently introducing seemingly unnecessary changes in syntax, making their documentation incompatible with existing compiler implementations - and I'm getting tired of trying to catch up.
I'm thinking of moving to PostCSS with a small subset of features, like nested selectors, to stay close to the CSS specs and hopefully one day we can do without any preprocessor.
---
Edit: The author of the posted link has an in-depth article on Sass, with much of which I heartily agree.
https://www.brycewray.com/posts/2021/04/speaking-up-for-sass/
swyx · 2022-08-09
gruez · 2021-12-07
> Google Fonts downloads are used for fingerprinting and browser identification: https://www.brycewray.com/posts/2020/08/google-fonts-privacy...
ctrl-F for "fingerpr": 0 matches
I skimmed the article and it looks like the only thing that's logged is your IP? Calling that "browser identification" seems like a stretch.
candiddevmike · 2021-12-07
One reason you may want to self host your fonts vs Google Fonts is to respect your users privacy. Google Fonts downloads are used for fingerprinting and browser identification: https://www.brycewray.com/posts/2020/08/google-fonts-privacy/