-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Discuss: Any changes to common subset for 2022 / v12? #3526
Comments
I wonder if in 2022 we still need all 4 CSS variants:
Also |
@allejo Any thoughts? |
I feel like with the widespread support and usage of CSS "variables" (aka custom properties), the need for CSS preprocessors has lessened significantly compared to a few years ago. Unless you're building a CSS library, chances are, you probably won't be writing in a preprocessor anymore. I think if the common subset only had CSS, that would suffice for people. Regarding Makefile... I don't think it's popular enough to deserve being in the common subset. It's mostly used in the C/C++ ecosystem and maybe Python. I vote to remove it. I'm on the border but I'd push to remove Also on the border, but I'd vote out Objective-C. Swift has largely taken over the Apple SDK ecosystem where I don't see a need to bundle it as being common anymore. You have my +1 for WASM and GraphQL |
These have been added and will hit with 11.6, only about ~750 bytes file size increase. I think I'm with you - we'll try to be a bit more aggressive this year with our removals - and if anyone yells too loudly we can always slip things back in, otherwise I'm probably likely to leave in some of this stuff for years to come... |
Removing:
|
Related: #2848
Time for yearly/release cycle of discussing any changes to the default
common
set of languages we bundle. v11 was released in May of last year and we do have things on the breaking changes list so I'm starting to think about a summer release of v12.The list stands at:
And the stats:
Rather than rehash what "almost" happened last time I'm just going to start this discussion fresh. We have since added two "hot" new web-related grammars that aren't currently in common that are worth consideration:
I'm not sure why we never added Node REPL last time but we probably should now for parity.
Opening this up for discussion.
CC @highlightjs/core
The text was updated successfully, but these errors were encountered: