W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2017

Re: [csswg-drafts] [css-values] Radians considered useless without π

From: Christoph Päper via GitHub <sysbot+gh@w3.org>
Date: Thu, 14 Sep 2017 08:12:33 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-329407956-1505376743-sysbot+gh@w3.org>
I have already scaled back heavily on my W3C activities, for a large part due to frustrating experiences like this. I basically only do small proposals such as this one any more. I haven’t thoroughly reviewed a spec in years because the discouraging feedback I often got (if any). I have seen issues being revisited more than a decade after I (or others who have moved on long ago) suggested to fix them, and been brushed off. The web is full of rants by authors about other annoyances, big and small, that had also been identified early on, and ignored. Many of those cannot be fixed any more; this one can.

I really don’t buy your argument and I tried to explain why. The few minutes or hours this would take once to implement in dozens of places by a handful of people do accumulate. I get that. But the seconds saved in writing and reading code by thousands of people in millions of places also accumulate. I’m not claiming that I could estimate the benefits and costs any more accurate than that, but, while CSSWG members probably have better insight in the latter, I strongly feel this imparts their judgment of the former, which is hardly better informed than mine. 

When in doubt, the Priority of Constituencies would demand that the author-friendly feature be added, but you are convincing yourselves that you were not in doubt in the first place so you can still feel like following that noble principle even when you are really not.

I understand that a feature that *might* be convenient needs additional justification, but I do not understand why a feature that *would* be convenient also does. Nobody challenged the fact that `pi` or `pirad` would be a useful unit to have in CSS. The only counter argument is cost of implementation. 

-- 
GitHub Notification of comment by Crissov
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/309#issuecomment-329407956 using your GitHub account
Received on Thursday, 14 September 2017 08:12:26 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:18 UTC