148 karma · joined November 2, 2011
These are presumably the same kind of people that think anything that's source code is some kind stuff that lays magical golden goose eggs, regardless of how trivial it is -- or even if it's open-source.
IMHO there is a much bigger, broader problem with non-technical people in positions of influence (and even the general public!). It's this same kind of disconnect that leads to mountains of trivial patents being filed. (I can't even count how many times I've heard of an engineer being put in a situation where they're told they need to patent some of their work, regardless of whether the engineer(s) think it's worth doing.)
More worrying is that it's often not possible to persuade someone who is swayed in the wrong direction, because they just don't have the base level of knowledge to allow it.
On this point I almost want to say that every person who graduates from High School ought to have gone through a rigorous class in logic and another in statistics. It's all well and good to say everyone should have "critical thinking" skills, but you can't get there without some pretty solid intellectual tools.
I hit a wall in calculus 2 in University, because previously I had been able to rely on simply showing up and not putting in much effort to still do "pretty good". That was the first time I did poorly in any math/science course, and was a pretty big wake-up call. As a result, I ended up having to study more to fill in the gaps.
I was naive, came from a poor background with crappy public schools, and didn't think of math as particularly important to focus on until I saw how useful it was in physics. I don't think it's an all too uncommon story.
If you want more, use a different compiler, period. $VENDOR spends money on their compiler to support their chips, not to appease every whining, butt-hurt user on the Interwebz that thinks $BIGCO owes them something on a competing chip.
Right, because Intel should spend their finite resources buying every imaginable Intel-compatible CPU from other vendors just to test and qualify them for the Intel compiler.
http://blog.jooq.org/2013/08/24/mit-prof-michael-stonebraker...
And I think it just highlights a lack of understanding about what might make goto "bad" in programming--IMHO it's "bad" when it makes control flow more complex, which undermines maintainability. Common "cleanup" idioms that only jump forward are not that bad, because they don't make control flow particularly more difficult to follow. (Whereas jumping backwards, especially across many state changes, can be very hard to follow.)
Probably the most common (or at least my favorite) example of DCE leading to a surprise, is when embedded programmers use so-called "delay loops" which can be eliminated by the compiler because it too is "empty" (the loop produces nothing that is used outside of the loop).