The Trader Joe's model is an interesting comparison with the Costco model.
Similarities:
* Like you said, both have fewer choices than a conventional grocery store: if you want ketchup or peanut butter, there's only going to be one brand and one size.
* Both of them don't have scales at the registers: unlike at a conventional grocery store, nothing is sold by weight (which I'm sure provides another small efficiency gain).
* Both of them are cheaper than your typical grocery store.
Differences:
* I feel like Trader Joe's leans on store brand / white-labeling items more than Costco -- yes Kirkland Signature is a thing but Trader Joe's takes it further.
* The shopping experience is pretty different both in terms of the in-store experience and the quantities things are sold in.
* Costco requires a membership, Trader Joe's doesn't.
I wonder which elements of the two models would work best for a public grocery store.
To my ears it “since years” sounds like it’s missing an “ago” after it (or like the GP said “for years” sounds even more natural).
It makes me think of another similar one: I've noticed that British English speakers will say e.g. "the new iPhone will be available from September 20th"
To my ears that sounds like it's missing an “onwards” after it (or “starting September 20th” would sound even more natural).
This one drives me nuts. I get it if it’s a single page app, but in many cases right-clicking the same link and choosing “open in new tab” works fine so that’s not the issue.
Early Quakers rejected using different 2nd person pronouns for different people since it violated their principle of egalitarianism so they called everyone thee/thou (and got into trouble for it as you might expect).
I thought this was going to be about phonemes that used to be part of English but aren't anymore (e.g. all of the vestigal "gh"es in our spellings that used to represent the https://en.wikipedia.org/wiki/Voiceless_velar_fricative but are now either silent or pronounced as another phoneme).
Reminds me of when they finally apologized for the train wreck that was IE6 [1] and resumed Internet Explorer development in the 2000s after Firefox came along and started eating IE's market share.
In this case it's the MacBook Neo that's causing them to get off their butts and reinvest in the quality of their software after letting it stagnate for years, but the pattern is the same: rest on their monopolistic laurels until competition makes them feel threatened, then magically start caring about their users again all of a sudden.
I've heard that Waymo relies on having very accurate map data for the areas where they operate, so perhaps they could perform worse than human drivers in areas where they don't have good map data.
But I also trust that the company wouldn't deploy them in those areas until the quality data they need is available. So perhaps "safer in the environments where they are actually deployed" would be more accurate, but that's also the only thing that matters.
Speculating about what would happen if they were used in ways they are neither intended to be used nor are actually used feels a little silly. Most machines can be unsafe if you use them in ways they're not intended to be used.
It was a great piece and I learned a lot, thanks for writing it. I hope you didn’t think that it was you I was disappointed with rather than the language designers :)
It’s ironic how context cancellation has the opposite problem as error handling.
With errors they force you to handle every error explicitly which results in people adding unnecessary contextual information: it can be tempting to keep adding layer upon layer of wrapping resulting in an unwieldy error string that’s practically a hand-rolled stacktrace.
With context cancellation OTOH you have to go out of your way to add contextual info at all, and even then it’s not as simple as just using the new machinery because as your piece demonstrates it doesn’t all work well together so you have to go even further out of your way and roll your own timeout-based cancellation. Absurd.
It’s great that they identified this (incredibly common) pain point and introduced a way to solve it, but I can’t help being disappointed.
Reading the examples I found myself thinking, “that looks like a really useful pattern, I should bookmark this so I can adopt it whenever I write code like that.”
The fact that I’m considering bookmarking a blog post about complex boilerplate that I would want to use 100% of the times when it’s applicable is a huge red flag and is exactly why people complain about Go.
It feels like you’re constantly fighting the language: having to add error handling boilerplate everywhere and having to pass contexts everywhere (more boilerplate). This is the intersection of those two annoyances so it feels especially annoying (particularly given the nuances/footguns the author describes).
They say the point is that Go forces you to handle errors but 99% of the time that means just returning the error after possibly wrapping it. After a decade of writing Go I still don’t have a good rule of thumb for when I should wrap an error with more info or return it as-is.
I hope someday they make another attempt at a Go 2.0.
You’ve got the first two backwards. The real accountability mechanism in the constitution for a rogue president/administration is impeachment by congress (which is a proxy for the people in theory). Unfortunately neither enough of congress nor enough of the electorate cares if the administration breaks the law.