News for hackers. Stuff that matters.

A comment on State of CSS. Parent comment

Re:State of CSS by naillo on Friday October 21, 2022 @01:43PM (#33290845)
I guess all these additions are incentivized by google etc loving the fact that it makes the moat to make competing browsers wider and wider. Imagine trying to make a new browser from scratch in 2022 and supporting the 20+ years of bloat like this (not to mention future plans).
[ Parent | on HN ]
Re:State of CSS by asiachick on Friday October 21, 2022 @02:52PM (#33291698)
Did you even bother to look which browser implemented the features first? Will you update your priors based on what you find?
[ Parent | on HN ]
Re:State of CSS by naillo on Friday October 21, 2022 @03:11PM (#33291913)
I'm talking about the growth of features in general. Calm down no need to be so aggressive.
[ Parent | on HN ]
Re:State of CSS by pie_flavor on Friday October 21, 2022 @04:40PM (#33292801)
No need to be so conspiratorial either. Generally features make it in because they improve developers' experience.
[ Parent | on HN ]
Re:State of CSS by dmitriid on Friday October 21, 2022 @05:15PM (#33293118)
They are mostly one-off features that don't create a coherent whole. See what Figma has to say about this: https://www.figma.com/blog/building-a-professional-design-to...
[ Parent | on HN ]