"Security flaws caused by compiler optimizations" No. "exposed by" is not the same as "caused by". FFS.
-
Show this thread
-
There are cases where "caused by" is correct, but in those cases, the cause is "compiler bugs", not "compiler optimizations". The title as written is never correct.
5 replies 0 retweets 25 likesShow this thread -
Replying to @stephentyrone
I agree. it should be "Security flaws caused by poor language design" :p
2 replies 0 retweets 16 likes -
Replying to @whitequark @stephentyrone
(are the C and C++ committees totally captured by compiler people, or not yet? I've seen this argument but I don't know how much truth is there to it)
2 replies 0 retweets 0 likes -
Replying to @whitequark @stephentyrone
(*can* you have a language design committee that is not full of compiler people in the first place? is there a fundamental conflict of interest?)
5 replies 0 retweets 4 likes -
Replying to @whitequark @stephentyrone
it's extremely hard to extend a language in a coherent way without a formalism/reference impl or significant participation from compiler devs. so if you don't do compiler stuff, it can be easy to get disenfranchised as all your proposals get rejected for soundness issues
3 replies 0 retweets 6 likes -
see for instance one of my favourite PL design nightmares that should ideally be quickly thrown out by a proper model or domain expertpic.twitter.com/dp2o9msrrr
1 reply 4 retweets 22 likes -
In the case of Dart, that particular decision is simply because Lars Bak hates PLT.
1 reply 0 retweets 3 likes -
In general Google has a weird habit of putting people who hate PLT in charge of language design. I can *certainly* sympathize with not wanting to get carried away by theory, but the other extreme is not the solution. Heljsberg is a lot more sensible than Bak or Pike.
1 reply 1 retweet 16 likes
If there’s one thing I’ve learned over the past decade of work in PL, it’s that ideologues of any kind are virtually never the people you want in charge of language design.
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.