- From: Ryan Johnson via GitHub <noreply@w3.org>
- Date: Thu, 06 Nov 2025 22:50:49 +0000
- To: public-design-tokens-log@w3.org
> I tend to be in favour of more rigid specs to keep developers accountable, and therefore would not be in favour of this change. Developer accountability shouldn't be the responsibility of the spec authors. It's the spec itself that defines the baseline of what tools need to support, not the other way around. If tools wish to remain competitive and relevant, maintainers will need to plan on keeping up with the spec throughout the lifespan of the tool. While it's not always practical to maintain 100% compatibility, the tool _will_ eventually need to support newer versions of the spec, in order to remain competitive. -- GitHub Notification of comment by CITguy Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/342#issuecomment-3499710060 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 November 2025 22:50:55 UTC