799 karma · joined March 25, 2012
I kind of agree with your overall point, but that definition is wildly incorrect.
[1] https://www.wired.com/2016/05/monsantos-roundup-herbicide-ca...
I like your second point more, but the reality is that at the moment the risks seem tiny and the benefits are fairly large. There is essentially no way to prove that any technology doesn't have subtle, negative externalities (what kind of evidence would you like to see?) and in practice any "rule" so risk adverse that it bans GMOs would also ban many, many modern conveniences (for example, cell phones). Is that a net positive? I don't think so, but I know some people who might.
Three is a bit generic so it's hard for me to argue. Yes, industry support for "independent" science is problematic, but the problem swings both ways. Supplements and "health food" are a massive industry and sponsor research/lobby the government the same way Monsanto does. That being said, it's unfortunate that companies muddy the waters, but the bottom line is that there is essentially no credible evidence that GMOs are in general harmful to humans and a lot of evidence that they are not. (Additionally, you used the word "most", which implies that you know of at least some studies that do not have industry funding and declare them safe. Are those studies not conclusive enough for you?)
For four, "unadulterated food" seems clearly not perfect (at least to me) given the amount of time and energy that farmers spend trying to grow it. At the very least, you must surely agree that there is some variation in the desirability of "natural" plants. Doesn't that imply that not all "natural" plants are perfect? Additionally, the "unadulterated" food you buy in a grocery store has been bred over thousands of years to be more appealing, resilient, etc. Is it only the "natural" variety of the food that is perfect, or the version in the grocery store? If the latter, when did they reach the global optimum and at what point did any further variation become bad? Finally, if natural plants are perfect, how do you explain cost and risk sensitive farmers using the presumably less perfect GMO products?
If you're interested in a higher level hardware language, I'd highly recommend MyHDL or PyMTL. Both are much closer to Verilog (for better or worse) and give you higher level semantics.
Regardless, I appreciate that you're making an effort to be careful. I've just been seeing this particular study making the rounds on Facebook and I felt like I needed to point out what the study actually says.
Using the same precedence and associativity in declarations and normal expressions doesn't really help the compiler writer though, so I'm not sure how this supports your point. If anything, it complicates the parser by making it harder to decide if a given sequence of tokens is a declaration or an expression (e.g. the classic "a * b;" problem).
> In my view, a "user-oriented" declaration of an array of pointers would look like `pointer[10] of int`, and not `int *arr[10]`.
It sounds like you're saying that C's type syntax isn't easier to read than other, similar, possible syntaxes. On that, I completely agree (in fact, I think C's type syntax is horrendous). However, that's orthogonal to the issue of Dennis Ritchie's original intent when designing C. From his writings at least, it seems like he wanted to make it easy for the programmer to reason about the syntax and I'd even argue that he took steps to complicate the compiler to accommodate his chosen syntax. I'd also argue that he failed horribly in accomplishing his intention and the syntax you're describing would have been much easier to read.
Err, I would agree with the statement that the syntax of C (mostly) favors the compiler writer, but "declarations mirror use" is decidedly not a good example for a couple of reasons:
1. The grammar for type declarations is actually quite complicated[1]
2. Agol, which inspired C's type system, actually had a much more "compiler friendly" type syntax[2]. C's syntax is designed to be more programmer friendly.
3. Dennis Ritchie makes it pretty clear that "declarations mirror use" was intended to make use and declarations visually similar, which implies that it was done for the benefit for the programmer[3].
[1] Compare https://www.lysator.liu.se/c/ANSI-C-grammar-y.html to [2].[2] http://www.csci.csusb.edu/dick/samples/algol60.syntax.html#5...
[3] "Analogical reasoning led to a declaration syntax for names mirroring that of the expression syntax in which the names typically appear...In all these cases the declaration of a variable resembles its usage in an expression whose type is the one named at the head of the declaration." from http://www.jslint.com/chistory.html
https://upload.wikimedia.org/wikipedia/commons/d/d8/USA_annu...
Both GCC and Clang have __builtin_add_overflow, which as far as I can tell do exactly what you're proposing.
From 6.5.2.1 (Array Subscripting) of the C11 draft:
"A postfix expression followed by an expression in square brackets [] is a subscripted designation of an element of an array object. The definition of the subscript operator [] is that E1[E2] is identical to (*((E1)+(E2))). Because of the conversion rules that apply to the binary + operator, if E1 is an array object (equivalently, a pointer to the initial element of an array object) and E2 is an integer, E1[E2] designates the E2-th element of E1 (counting from zero)."
From 6.5.6 (Additive Operators):
"When an expression that has integer type is added to or subtracted from a pointer, the result has the type of the pointer operand. If the pointer operand points to an element of an array object, and the array is large enough, the result points to an element offset from the original element such that the difference of the subscripts of the resulting and original array elements equals the integer expression. [...] If both the pointer operand and the result point to elements of the same array object, or one past the last element of the array object, the evaluation shall not produce an overflow; otherwise, the behavior is undefined."
To me, those sections together read that there should be no overflow as long as i is smaller than the length of `points` + 1, and thus no undefined behavior. Does anyone have another interpretation?
That's the fundamental problem. It turns out with a reasonably accurate test, a low incidence rate, and a large population, the "definitely X" class will be filled with people who aren't actually X. Going back and trying to separate the two ends up costing more and causing more harm to the non-Xs then just waiting until there's a problem. I'd encourage you to take a look at the link I posted since it takes a very clear look at the problem in the context of mammograms and breast cancer.
> Their assertion that tests === diagnostics that map 1:1 to a disease was baseless. Tests don't answer the question "doe patient have diabetes?", they answer the question "what is the patients glucose level?" 115 mg/dl.
Medical tests that aren't actionable aren't useful. So while you're correct in a very narrow sense, you have to use the results to make a decision about treatment. If you're going to make treatment decisions based on tests that have some amount of inherent error, you may end up over or under-treating patients.
> Maybe the patient forgot to fast, maybe the test was a fluke? Either way a consistent average of 85 would put that out of range.
Medical tests have both random and systematic error. What you're talking about is random error (i.e. a single test result being bad). However, many tests have systematic error (i.e. the result being wrong every time the test is taken) just due to personal variation in what's "normal".
The article makes the point that if more tests lead to worse outcomes[1] (due to overtreatment) then adding more tests is useless or worse than useless. This effect is particularly pronounced when testing across large populations, even if the test is highly accurate.
[1] And in many cases they do. For example, early mammogram screenings result in worse outcomes for patients when done across a large population. See http://annals.org/article.aspx?articleid=2480757
Let's be a little more conservative. Suppose you spend 25% of your post-tax income on housing. A 125k income supports a $1750/month payment, which works out to a ~370k house. That gets you a median house in all but 3 states: Hawaii (556k), DC (550k), and California (462k) - the next state up is Massachusetts (343k). You could also buy the median house in all but 16% of zip codes.
I couldn't find that much data on school districts, but just as a point of comparison, 370k is enough to buy the median single family home in 7 of the top 10 school districts in Michigan[2]:
1. 350k, Bloomfield Hills Schools
2. 411k, Birmingham Public Schools
3. 219k, Okemos Public Schools
4. 429k, Novi Community Schools
5. 343k, Ann Arbor Public Schools
6. 276k, Saline Area Schools
7. 370k, Troy School District
8. 285k, Grosse Pointe Public Schools
9. 335k, East Grand Rapids Public Schools
10. 429k, Northville Public Schools
If you bumped up your payments to about $2023/month (~29% of post tax income in Michigan) you would be able to afford a median single family home in every top school district (~430k).Also, anecdotally, I grew up in Michigan and a 400k home was solidly upper-middle class even in nice areas like Ann Arbor and Bloomfield Hills. In Ann Arbor, a 600k home would be either a mansion or a family home in an extremely desirable area.
[1] http://www.zillow.com/research/data/ [2] https://k12.niche.com/rankings/public-school-districts/best-...
This is a bit of a tangent, but Michigan actually has fairly high construction standards for roads. However, it also has one of the highest truck weight limits in the nation (over double the federal limit) and most road damage comes from heavy trucks.