> I'm surprised they didn't eat it up until new releases when they often increase prices.
There may be an element here where announcing new hardware at a 30% higher price would largely make the latter the focus point, so instead they chose to take the hit of the price hikes separately.
> convincing someone that their excessive null checking is harmful is an uphill battle.
The argument that seems to hit home more often than not is that optionals effectively “fork” the state space, the possible states your program can be in. And the larger the state space is, the harder it is to reason about the code and maintain it. That’s actually part of what make undesirable states un-representable means.
Exactly, plus you now have a new superpower with AI — the ability to dig into and ramp up expertise in mostly any domain. I’d say the article gets it backwards.
Wait, what? Double-clicking will prompt for Face ID to open your default card for oayment, and from there you swipe down to see the stack — which I suppose is the screen you’re looking for.
Exactly. The principle to go by for estimates is finding a balance between time/scope/cost, and figuring out which aspects of the context affect which dimension is the first step.
I’ve no experience with Elastic but what they’re getting at I think is indexes in Elastic is actually your data because that’s all it does due to the purpose it was built for, whereas in Postgres indexes are, well, indexes — that is, derived data, not the source of truth.
Agreed. I think you may be too generous with hubris -- that requires agency, but it may just be incompetence. I don't generally like the "old days" argument, but this is consistent with overall trends -- it's frivolous.
What feels plausible to me is changing the underlying 19x19 px control would break layout of many existing apps, and the design team was hell bent that window corners had to be that round. I’d say it’s simply form over function, and that likely a meta-level argument about user empowerment or whatnot won.