- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Apr 2022 06:40:45 +0000
- To: public-design-tokens-log@w3.org
> This issue is saying "hey, parsing strings to get numbers is dumb; we should just separate the data in the format itself instead of parsing a string." No one said anything like this or used a tone like this. Please do better! ----------------------- The main issue I see with this specification proposal is that it is focussed on creating an interface between multiple programs but too many provisions are made for reading and writing by humans. This does have a short term advantage which I fully understand. But as more and better tools are created to interact with token files the need for this will largely go away. > Parsing numbers and units from a string is trivial and performant in every programming language. This might be true in practice but this specification will still need to define exactly how values must be parsed. Any specification which has micro syntax does this to avoid interop issues. This places extra burden on editors of the spec and implementers. This can not be debated away. It is work that has to be done. Avoiding micro syntaxes altogether and choosing to create a data format without any possible ambiguity is possible. I am only advocating for making the choice in favour of something that works best as an interface between multiple programs. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/121#issuecomment-1085492980 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 April 2022 06:40:47 UTC