I'm holding myself back from fighting really hard. Your shrug is the thing that enrages me.
-
-
please try to understand why 1. There may be important use cases, 2. Security by 1/
1 reply 0 retweets 0 likes -
"every developer should evaluate risks" does not comport with modern security practices 2/2
5 replies 0 retweets 0 likes -
Replying to @wycats
: 2) Developers should evaluate risks, just like they evaluate performance tradeoffs, etc.
@mikesherov@SlexAxton@The_Brown_Shoe1 reply 0 retweets 0 likes -
Replying to @mikewest @mikesherov and
in general, devs use tools that help make trade-offs for them. In this case, there's 1/
1 reply 0 retweets 0 likes -
nothing ember can do to acquire the eval capability safely cuz no one designed the API 2/
1 reply 0 retweets 1 like -
and in general the attitude is "shoot capabilities first, ask questions later" 3/3
1 reply 0 retweets 1 like -
because it's "opt in" granularity is never seen as a high priority, but security teams 1/
1 reply 0 retweets 0 likes -
are eager to opt in (I'm sure you think this is good), but that means in practice I 2/
1 reply 0 retweets 0 likes -
am forced to contend with ungranular policies I can't make more granular. 3/
1 reply 0 retweets 0 likes
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
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.