any policy that disallows dynamic evaluation of JS as a "broken legacy feature" is bad imo
are eager to opt in (I'm sure you think this is good), but that means in practice I 2/
-
-
am forced to contend with ungranular policies I can't make more granular. 3/
-
in practice this means I advocate for the feature to be turned off entirely and 4/
-
explain why it's low risk in ember apps, but this isn't what we want. 5/5
End of conversation
New conversation -
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.