Browser London
browserlondon.com · Company blog · on HN since 2013
Browser London is a digital agency whose blog covers front-end development, project methods like user stories and MoSCoW, and CSS approaches.
What HN saysHN cites it in Tailwind and atomic CSS arguments, mostly its post on the perils of functional CSS, though one commenter notes it contradicts its user-story stance.
18HN people shared it
4linked it in comments
27stories submitted
70story points
1 year agolast shared
2013people per year2026
Most-shared posts
- 1The Perils of Functional CSS6 people · 6 points · first shared 2019 · 1 comments on HN
- 2Why user stories belong in the garbage2 people · 26 points · first shared 2022 · 10 comments on HN
- 3The Power of the MoSCoW Method2 people · 4 points · first shared 2019 · discussion on HN
- 4The issues with JAMStack: You might need a back end2 people · 4 points · first shared 2020 · 1 comments on HN
- 5Apple’s move to ARM could reshape the development landscape2 people · 3 points · first shared 2020 · discussion on HN
- 6Continuous improvement beats big ‘tada’ releases2 people · 2 points · first shared 2023 · discussion on HN
- 7Front End Predictions for 20211 people · 4 points · first shared 2021 · discussion on HN
- 8React is king (and that’s not changing anytime soon)1 people · 3 points · first shared 2021 · 1 comments on HN
- 9What dependency hell looks like, and how to avoid it1 people · 2 points · first shared 2020 · discussion on HN
- 10How to "Break" Your Design System Rules Without Creating Chaos1 people · 2 points · first shared 2025 · discussion on HN
- 11Front-End Developers, Pick Your Battles Wisely1 people · 2 points · first shared 2017 · discussion on HN
- 12Why small teams are mighty1 people · 2 points · first shared 2019 · discussion on HN
- 13SVG Gradients: Solving Curved Challenges1 people · 2 points · first shared 2023 · 1 comments on HN
- 14A Night of TDD and Full Stack BDD1 people · 2 points · first shared 2013 · discussion on HN
- 15Reimagining the Semantic Web: UCL's Innovative Synthesis of AI and Web Science1 people · 2 points · first shared 2024 · 1 comments on HN
What HN people wrote when they linked it
dwmbt · 2021-11-04
i 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-utility-classes-and-separation-of-concerns/
[2] https://acss.io/thinking-in-atomic.html
and finally, it's always useful to read critiques. the following article is well written, in my opinion: https://www.browserlondon.com/blog/2019/06/10/functional-css-perils/. through that i learned that tailwind has a useful feature: @apply, which you can use in conjunction with a standard css class approach. i.e
container
{
@apply color-grey-100;
box-sizing: border-box;
}
x3n0ph3n3 · 2022-09-03
Kind 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-mapping-chang…
suyash · 2020-05-08
Atomic CSS is a bad idea, read more here https://www.browserlondon.com/blog/2019/06/10/functional-css-perils/
sheriffderek · 2019-06-18
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-perils/ I just can't imagine not writing CSS like this: https://maintainablecss.com/chapters/introduction