3 ms·
>>what are you going to do if those proposals change, as the decorators proposal actually has changed? I'd just update my code to meet the spec. Likely it wou
by andrewstuart 11y ago
>>what are you going to do if those proposals change, as the decorators proposal actually has changed?
I'd just update my code to meet the spec. Likely it would take vastly less time than the hours needed to fail in configuring Babel. The documentation can just say "this feature isn't finalised, it might change." That's enough. The code does not need to be disabled just because the spec isn't final.
>> quite dangerous
It's not really dangerous. No-one is going to die. It's emotive words like dangerous that lead Babel developers to think "we'd better hide that functionality behind hard-to-configure barriers so people don't cut themselves on the dangerous code".
- thejameskyle 11y agoIt's extremely dangerous, we're talking about tens of thousands of developers who have chosen to depend on Babel for their livelihood, we can't just keep breaking things on them. We don't want Babel's configuration to be difficult, we just want people to explicitly tell us what they want. If you have suggestions on how to make the configuration easier I'm happy to hear it. But turning stuff on by default it a terrible terrible decision that hurts the community.