-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First pass at #453 (text-based syntaxes should be designed for humans) #472
base: main
Are you sure you want to change the base?
Conversation
Ideally, the syntax would be optimized for human usability, and tooling would optimize the syntax for efficiency. | ||
However, this is not always possible. | ||
In these cases, explore if it is possible to provide syntax that is flexible enough to accommodate both use cases. | ||
The downside of this approach is that it increases the complexity of the language, and humans may still need to read the less human-friendly syntax. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what this sentence is getting at. What less-friendly syntax are you talking about?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's talking about cases where you need two have two syntaxes, one optimized for efficiency and one for humans.
The downside of this approach is that it increases the complexity of the language, and humans may still need to read the less human-friendly syntax. | ||
Lastly, if efficiency is truly critical, consider whether a binary format may be more appropriate. | ||
|
||
<div class="example"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Therefore, optimizing it for human usability also makes it easier to develop tools to generate it. | ||
|
||
Human usability may often be at odds with parsing performance and filesize efficiency. | ||
Ideally, the syntax would be optimized for human usability, and tooling would optimize the syntax for efficiency. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was a little unclear as to what this line was trying to say; @LeaVerou explained it's about situations e.g. where you can minify a file with tooling to make it more efficient - that was good clarification I think, so I suggest including that in the text.
It feels like there could be quite big implications here (accepting tooling as integral to the process, if we've not already explicitly done so elsewhere). Solving for both human readability and efficiency is an important challenge.
💥 Error: 405 Method Not Allowed 💥
PR Preview failed to build. (Last tried on Feb 1, 2024, 4:56 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 CSS Spec Preprocessor - CSS Spec Preprocessor is the web service used to build Bikeshed specs.
🔗 Related URL
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.