Trying to avoid breaking existing content is already a hard enough job for standards (and very important in the general sense).
-
Show this thread
-
These occasional flare ups where hard-working standards folks (including web developers you probably respect) are attacked for being out of touch and "holding back the web" does nothing to make our job easier.
1 reply 2 retweets 13 likesShow this thread -
We already understand that the future is bigger than the past, and that we don't want to do something ridiculous to accommodate a handful of sites.
1 reply 1 retweet 4 likesShow this thread -
But we need to do our job, which means exploring the available options, estimate the expected amount of breakage, and ultimately make a decision that balances the factors correctly.
1 reply 1 retweet 4 likesShow this thread -
Right now, helping would look like brainstorming alternative names, thinking about technical ways to mitigate the damage (a la @
@unscopeable), and helping to empirically estimate how common the problem would be.3 replies 2 retweets 11 likesShow this thread -
(for example, how common, empirically, are bugs caused by the difference between the proposed spec and the in-the-wild implementation)
1 reply 0 retweets 3 likesShow this thread -
Also, we could discuss the possibility of adopting the in-the-wild semantics (flatten Infinity levels by default) on a dedicated GitHub issue.
1 reply 1 retweet 6 likesShow this thread -
All of that is careful but important work and you can help with it if you're interested.
1 reply 1 retweet 4 likesShow this thread -
Not helping: starting campaigns to "force" those "out of touch" TC39 "neckbeards" to "stop holding the web back". You're talking to real people who write JavaScript every day who are trying to do a job that is already difficult. Please send help.
5 replies 8 retweets 69 likesShow this thread -
If TC39 can only handle web dev input when it's not there or when it agrees with it, then there's no point to open source the discussion. I understand we can't design by committee on JS but there has to be at least some form of accountability and democracy in the process.
1 reply 0 retweets 0 likes
Lots of web devs are on the committee, fwiw. I don't think the convo was locked because people don't want to have the convo but rather because it was framed poorly ("should we accept smoosh"). Tons of productive open convos have happened in public. No reason to stop.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.