3 ms·
Fixed the autocorrect error. It is super meaningful - it helps identify potential issues in real world use-cases and it creates effectively a "market" of peopl
by BillinghamJ 8y ago
Fixed the autocorrect error.
It is super meaningful - it helps identify potential issues in real world use-cases and it creates effectively a "market" of people already using the feature who want to be able to use it without transpiling. It's also pretty rare that the implementation changes meaningfully after implementation into Babel from around stage 2.
- danShumway 8y agoI should have used a more descriptive term than meaningless. Transpiler implementations do not count as hard restrictions on whether or not a proposal can change in the future. They're allowed to do whatever they want -- the fact that they create demand is very useful, but should not be seen as a restriction on whether or not the standard can evolve past that point. "It's also pretty rare" is exactly the problem. They can change. When browsers ship a non-standardized behavior that's on by default, they are effectively cementing it. It is very hard to correct a broken implementation that is live, in the wild, on normal sites. The fact that these changes are rare doesn't make it less important to follow the established process. Stage 3 is one last safety check before the feature gets turned on for everyone. What is the point of having a stage 3, if browser makers treat it as equivalent to stage 4?