Top all-time · #4378
Browser London
Company blog · browserlondon.com/blogdesignweb
Browser London is the company blog at browserlondon.com, writing about design and web. Since 2013, 18 different Hacker News readers have linked it 31 times, most often “The Perils of Functional CSS”. It is still writing: the last post was on 2026-10-15, and you can follow it by feed.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link these posts when discussing CSS methodology, including functional CSS versus atomic CSS and Tailwind. One post on user story mapping is also cited in a thread about user stories.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Browser London is a UX UI design and development agency that specialises in user research-backed design validated by user testing.
Most-linked posts?
- The Perils of Functional CSS6 people · 6 mentions · first linked 2019-06-18
- The issues with JAMStack: You might need a back end2 people · 2 mentions · first linked 2020-04-21
- Why user stories belong in the garbage2 people · 2 mentions · first linked 2022-08-30
- Continuous improvement beats big ‘tada’ releases2 people · 2 mentions · first linked 2023-02-10
- The Power of the MoSCoW Method2 people · 2 mentions · first linked 2019-11-07
- Apple’s move to ARM could reshape the development landscape2 people · 2 mentions · first linked 2020-07-28
What Hacker News says?
Once you add all of those classes, it's nearly impossible to add a developer who isn't used to it. It's also really hard for me to read. Tailwind / bootstrap etc - is a total deal breaker for me. I'll just get a different client. https://www.browserlondon.com/blog/2019/06/10/functional-css... I just can't imagine not writing CSS like this: https://maintainablecss.com/chapters/introduction
Comment linking /blog/2019/06/10/functional-css-perils/
on “Relearn CSS layout”Submitted Why user stories belong in the garbage as a story · 23 points
HN discussionAtomic CSS is a bad idea, read more here https://www.browserlondon.com/blog/2019/06/10/functional-css...
Comment linking /blog/2019/06/10/functional-css-perils/
on “Rebuilding our tech stack for the new facebook.com”Submitted Front End Predictions for 2021 as a story · 4 points
HN discussioni would say the tailwind docs themselves and looking at the examples were a big help. for instance, the way they visualize their flex elements was enlightening. also, learning about how atomic css is a useful paradigm was the biggest motivator for writing more meaningful and expressive css. i'll list some things i've bookmarked: [0] https://css-tricks.com/lets-define-exactly-atomic-css/ [1] https://adamwathan.me/css…
Comment linking /blog/2019/06/10/functional-css-perils/
on “Goodbye CSS Modules, Hello TailwindCSS”Submitted Why user stories belong in the garbage as a story · 3 points
HN discussionKind of a weird hyperbole, given they recently wrote about how vital user-stories are and how awesome they are at converting them into tasks. [1] 1. https://www.browserlondon.com/blog/2022/05/11/user-story-map...
Comment linking /blog/2022/05/11/user-story-mapping-changed-how-we-deliver-projects/
on “Why user stories belong in the garbage”Submitted React is king (and that’s not changing anytime soon) as a story · 3 points
HN discussionSubmitted The Perils of Functional CSS as a story · 3 points
HN discussionSubmitted The Power of the MoSCoW Method as a story · 3 points
HN discussionSubmitted Reimagining the Semantic Web: UCL's Innovative Synthesis of AI and Web Science as a story · 2 points
HN discussionSubmitted SVG Gradients: Solving Curved Challenges as a story · 2 points
HN discussionSubmitted The issues with JAMStack: You might need a back end as a story · 2 points
HN discussionSubmitted What dependency hell looks like, and how to avoid it as a story · 2 points
HN discussionSubmitted Apple’s move to ARM could reshape the development landscape as a story · 2 points
HN discussionSubmitted The issues with JAMStack: You might need a back end as a story · 2 points
HN discussionSubmitted The Perils of Functional CSS as a story · 2 points
HN discussionSubmitted Why small teams are mighty as a story · 2 points
HN discussionSubmitted Front-End Developers, Pick Your Battles Wisely as a story · 2 points
HN discussionSubmitted A Night of TDD and Full Stack BDD as a story · 2 points
HN discussionSubmitted How to "Break" Your Design System Rules Without Creating Chaos as a story · 1 points
HN discussionSubmitted How to "Break" Your Design System Rules Without Creating Chaos as a story · 1 points
HN discussionSubmitted Continuous improvement beats big ‘tada’ releases as a story · 1 points
HN discussionSubmitted Continuous improvement beats big ‘tada’ releases as a story · 1 points
HN discussionSubmitted Is it smart to build an app on someone else’s platform? as a story · 1 points
HN discussionSubmitted Apple’s move to ARM could reshape the development landscape as a story · 1 points
HN discussionSubmitted Bad app QA derailed the US presidential primary as a story · 1 points
HN discussionSubmitted The Power of the MoSCoW Method as a story · 1 points
HN discussionSubmitted The Perils of Functional CSS as a story · 1 points
HN discussionSubmitted Atomic Design in Practice – Does It Work? as a story · 1 points
HN discussion
