So, the response is here. Without a closer look I can't say what's really going on - although I lean toward believing that Core is going in the right direction - but there still seem to be some orange flags.
Unfortunate. I'll wait some days for the response, but it better be a good one.
This behavior from Core may be par for the course, but I can already buy watches from companies that have values only for marketing. It's a small niche, and being nice would not cost much.
And they already died once, without having a proper off-ramp for their users - for now I don't trust them to exist in another two years. (I'm not really sure they even are in this for the long term - talk is cheap.)
And also, some tools still break when using the non-default umask.
Yes, yes, we all run Postgres in containers, but if you don't, and you upgrade to a new Postgres major version, gladly using the Debian scripts that make it all more comfortable, while using umask 027, you will enjoy your day. Though I don't remember if those upgrade-scripts where from Debian proper or from Postgres.
Since that experience I always wondered what other tools may have such bugs lurking around.
I once had a colleague from Iran. Working (legally) in the middle of the EU. He was already blocked from using credit cards, but thanks to not-100%-US-dominance still allowed to use local banks. For such local banking he will likely need to have Play services.
It's not countries that are affected, but people. And people sometimes move.
All these announces are scenery and promotion. Very low chance any of these "corrections" were not planned. For some reason, sama et al. make me feel like a mouse played with by a cat.
I'm not sure if you are serious or joking. "6 degrees of separation" is the famous radius for how many steps are needed such that everyone is connected.
Once you know your grinder, too high a max pressure is not so much of a problem, as choking a shot becomes a rare issue.
Consistently good Espresso is easier using a slightly coarse ground, but something needs to give, like texture or concentration.
Taken together, cheap machines can work well, although learning on them can be frustrating.
Use fresh roasts, and use them up quickly. Some days after opening a bag of not single dose frozen beans , many coffees lose their good aroma, and only the roast itself remains.
Not nicely put, but not wrong. I had half an heart attack when that feature was rolled out, and the danger was split only between myself and a colleague. I can't even trust myself to not screw up. I needed another permanencied invocation of the principle of hope.
Both the bug list and the reaction to it are deeply concerning, if you are depending on this project - but I don't know how much real world use this code gets.
Shows that reviewing dependencies is not optional. Hundreds of stars on GitHub is not a helpful data point, even if my own monkey brain says otherwise.