716 karma · joined September 11, 2009
To some people, but not everyone. It doesn't make sense to give unqualified "bests" without these kinds of caveats.
I don't personally share this view. I don't think growth or wealth are inherently good.
For example, if the goal is a fair society, then we should have a wealth tax, to disincentivize wealth equality. (And an income tax isn't so bad either in).
Having only a consumption tax makes sense if the goal is (only) to reduce consumption.
We've lost our ability to just "be". We must always "do". A sad state of affairs.
As others have pointed out, this article doesn't actually explain why (or even if) Honeycrisp has gotten worse. One thing I will add to this discussion, though I don't know if it is true in the case of Honeycrisp, is that it is definitely not a matter of breeding (nor selective breeding, breeding for storage, etc): in order to produce more apple trees, Honeycrisps (or any other variety) aren't bred, they are asexually propagated through grafting. That means all Honeycrisp trees are more-or-less genetically identical.
That said, just like any organism, as trees grow and produce new cells at the tips of branches, there is always a chance for a mutation. Sometimes these branch mutations (called "sports") have visible genetic differences: stronger coloration, earlier ripening, or perhaps earlier storage (though this is harder to notice). This is how Red Delicious went from a wonderful apple to tasteless, mealy cardboard: sports were selected over time that prioritized storage and color over texture and flavor.
As an apple grower, I have had the opportunity to taste Honeycrisps straight off the tree, and to me, they taste just as flavorless as the ones I get from the store. I grow almost all heirloom varieties, and I can tell you there is one that for me is head-and-shoulders above the rest: Wickson Crab. If you are in California, I recommend marking your calendar for September to search this variety out at the farmers markets (or better, plant a tree yourself!). There are many other wonderful varieties that stand out from grocery store apples. In a pinch, I'll get a Pink Lady from the store, as I find it's the most flavorful of the commonly available apples, but I find they sit heavy in my stomach in a way that homegrown or farmer's market apples don't. I believe this is to do with the fact that apples available at the grocery store are picked early, before the starches have converted into sugars, so the higher starch content may be harder to digest.
Hint: any apple with an "apple green" undercoat is underripe; to pick a ripe apple, wait for that bright green to mellow out or change colors. For redder apples, it can be harder to see, but most apples have some green visible under the red (Pink Lady is again a great example of this). And yes, Granny Smith apples are so sour precisely because they are picked and sold underripe; a ripe Granny Smith is yellow and sweet.
Presto and SparkSQL are SQL interfaces to many different datasources, including Hive and Impala, but also any SQL database such as Postgres/Redis/etc, and many other types of databases, such as Cassandra and Redis; the SQL tools can query all these different types of databases with a unified SQL interface, and even do joins across them.
The difference between Presto and SparkSQL is that Presto is run on a multi-tenant cluster with automatic resource allocation. SparkSQL jobs tend to have to be allocated with a specific resource allocation ahead of time. This makes Presto is (in my experience) a little more user-friendly. On the other hand, SparkSQL has better support for writing data to different datasources, whereas Presto pretty much only supports collecting results from a client or writing data into Hive.
I do agree that CA seems to be doing what it can to be combating the disease.
And who ends up winning? Web developers everywhere. I don't see why this is a bad thing.
I don't know exactly, but I assume this is because I know what goes on behind the scenes, and 99% of the time, the website is doing way more work than it really needs to in order to deliver the experience that I'm asking for.
(My one open question, and something this page doesn't touch on, is how easy is it to get ToroDB up and running? Mongo makes that part easy as well!)
I thought you meant that clients A and B do their writes, and only if someone at a later time were to observe the value at that key, a conflict would be caused (Heisenberg-style).
Thanks for clarifying!
because there are no reads, any serialization order is possible and therefore there is no chance of conflict
I don't understand how this is the case. If clients A and B try to write to the same key, it can be serialized as {A,B} or {B,A}, but in either case, there is some kind of conflict... no?