I suspect that they feel at least incrementally less burned in this case; since, while it wasn't obviously a good idea for a product, it at least goes somewhere: if you can make a phone functional and adequately rigid at that size; it's quite possible that there's a more sensible device size that you can still apply the miniaturized motherboard and whatever mechanical engineering you did for rigidity to; and just fill the rest of the case with battery; and there may be some other cases where the ability to get an entire SoC and supporting components into a particularly tiny area or make a thin component of a larger system quite rigid is handy.

Still doesn't really explain flaying a normal phone until it barely has a normal day's use with a totally fresh battery when you are still going to glue an entire baby spy satellite to one end of it; but some of the actual engineering is probably reusable.
The 'butterfly' keyboards, or the under-mouse charging port, by contrast, went nowhere. They tried and failed at a few iterations of keyboards that committed expensive suicide if you looked at them wrong; then just went back to allocating the extra mm or whatever once Jony was safely out of the picture; and it's not as though putting the port on the bottom rather than the front of the mouse involved any interesting capability development.

Whatever product manager thought that the 'air' would be a big seller deserves to feel bad; but the actual engineering team can probably feel OK about the odds that a future phone will look somewhat air-like if you were to remove the normally shaped case and larger battery.

At 2013, the disks in question were spinning disks. I didn't understand from the article whether the stats for 2021 and 2025 were about spinning or solid state drives.

Comparing reliability over time of spindles to solid states is almost meaningless. The failure scenarios are just not the same.

Two questions:

1. Did you have a choice? Was there an option, maybe even a more expensive one, that did not include the lock-in?
2. Is the company where you signed the contract a monopoly?

Because what usually happens is that you don't have a choice but to sign this contract, or you can't get the service at all.

It's stupid; but at least more honest than trying to dress 'grok' up as the master control computer.

In the MS case; it wouldn't be too surprising if that order is also the one that urgency dictates. Neither is totally unavailable on-prem only; or entirely without more-chatty-than-one-would-like behavior; but if your concern is about your dependence and Redmond's potential direct control their groupware stuff is moving faster than their OSes(at least if you have enterprise licenses and someone to handle keeping them quiet) in the direction of pure SaaS.

You'll get some nagging about how Azure Arc is definitely the cool kid's future of glorious hybrid manageability; but your ability to run Windows as though it were 15 years ago is definitely greater than your ability to run Office that way.

I suspect that this won't be the last case we see; as MS has shown comparatively little interest in backing down on the future being azure SaaS, and there's no real equivalent to some steep but temporary discounts for dealing with people who have fundamental privacy and operational control issues; while it's not terribly challenging to find a special discount that makes sticking with the status quo look cheaper than trying to do a migration.

I obviously don't expect better from these sorts of people; but I'm honestly puzzled as to why they would turn the screws so quickly and blatantly despite having gone to all the trouble of a reshuffle and a new lineup and some spiel about being likeable rather than Alexa just being something that you sort of poke at because Prime members were given a free surveillance puck with some offer one time.

Is Panay one of those abhuman lunatics who genuinely thinks that the only objection to relentless advertising is that it isn't "relevant" or "engaging" enough? Does he have a scorpion nature that leads him to knowingly doom his own product just because that's what he is? Is he just a figurehead who got to choose the case plastics colors and smile on stage; but some adtech business unit calls all the shots?

I'd fully expect this sort of thing to betray you; but only after enough of a honeymoon period for people to be pleasantly surprised by the behavior of the launch units so that there is actually enough of an install base to betray.

It sure is a good thing that 'AI' companies are notoriously discerning and selective about their training inputs and not doing something risky like battering on anything with an IP address and an ability to emit text in the desperate search for more; so this should be a purely theoretical concern.

Snark aside, I'd be very curious how viable this would be as an anti-scraper payload. Unlikely to be impossible to counter; but if the objective is mostly to increase their cost and risk when they trespass outside the bounds of robots.txt something that will just look a trifle nonsensical in places to a human but could cause real trouble if folded into a training set seems like it could be quite useful.

It can certainly be done otherwise; but it's not exactly unrelated when, in practice, a TPM is the industry standard mechanism for making a PC or PC-like system capable of cryptographically secure remote attestation; and when TPMs quite specifically mandate the features you need to do remote attestation rather than just the ones you would need to seal locally created secrets to a particular expected boot state. They are certainly can do that, and it's presently the most common use case; but locking down remote attestation was not some sort of accidental side effect of the design.

The place where TPMs potentially get toothy is remote attestation. As a purely local matter having your boot path determined to be what you think it is/should be is very useful; but, by design, you can also request that from a remote host. Again, super useful if you are dealing with a nasty secure orchestration problem(Google has a neat writeup of how they use it); but also the sort of thing that is potentially tempting for a relying party to use as part of authentication decisions.

We've seen hints at related issues on the Android side; where hardware attestation API or 'Play Integrity' API demands are made by some applications that block 3rd party ROMs, even if the boot sequence is entirely as expected(and even if the 3rd party ROM is almost certainly in much better shape than the first party one; eg. Graphene vs. some out-of-support entry level Samsung); which has chilled 3rd party ROMs considerably.

If relying parties who are important(ISPs, banks, etc.) do start demanding attestation the situation in practice becomes a great deal more restrictive.

I suspect that the answer involves a hard look at where the wealth ends up, which is likely why there's limited appetite for tugging at that thread; but what I don't grasp about the Baumel explanation is why the cost goes up relative to the typical ability to pay; rather than mostly staying level.

The fact that productivity largely hasn't budged is certainly an explanation of why professors or nurses haven't followed the cost of transistors or TVs; but if something like education's cost increases are being driven by what they need to pay people who could work in a different industry; why do people who do work in that different industry not see the cost as more or less constant in relative terms, rather than steadily creeping up over time?

What baffles me about these stories of financial unsustainability in higher education is just where exactly all the cost comes from. I realize that thereâ(TM)s the opportunity cost of ~4 years of not working/part timing around classes; and that there are some particular subjects that need a large hadron collider or some cryogenic longwave IR space telescopes or a BSL4 virus lab; but I just donâ(TM)t understand how âoetake professor who is tenured but earns more or less fuck-all for someone of their experience and qualifications, or adjunct who isnâ(TM)t tenured and earns even less, provide whiteboardâ has somehow become a crushing financial burden for what are supposed to be wealthy, developed world, societies.

Same general confusion with parts of medicine; obviously Iâ(TM)m not expecting novel monoclonal antibodies or cutting edge oncology for $3.50; but why does it cost so much to speak to a GP for 30 minutes and get some 40 year old generic; or get a nasty cut checked for foreign objects and stitched up at the ER?

What strikes me as curious about this hypothesis is that it has been the case for decades. It wasn't "AI"; normally some combination of overgrown Excel sheets and garbage-tier Access by the more technical of whatever the mostly nontechnical user population happened to be to deal with needs that didn't get developer attention. And, for the most part, they still didn't get developer attention.

I suppose that there is a slim possibility that this 'vibe coding' will somehow convince management in ways that Access didn't, by being better at giving the illusion of being a slick solution that just needs a little more fixing; but there's nothing about the past quarter century of no-code/low-code or the last more-or-less-forever of "understand what it is your employees do and what would be useful for doing it" that suggests that people are particularly good at getting software to those in need of it.

If 'AI' tooling makes it radically cheaper to actually get to a final, working, tool then perhaps it will increase the absolute number of programming jobs if 'dude from fivver' replaces 'access' as the de-facto barely adequate unmaintainable solution; but if the idea is that somehow 'AI' will increase the number of actually costly programmers getting thrown at problems because it's easier for amateurs to produce broken non-solutions that seems implausible given the history. If it does happen, it will mostly be an indictment of everyone who could have used technology we had in 1925, the venerable "look at your fucking business processes and ask your more competent people some questions, dumbass" to identify gaps; and I suspect that it mostly won't happen. You'll probably get some projects that are mostly about saving face for whoever vibe-coded their way into the problem and overpromised; but it's not like the bot codebase will be more useful to the programmer than the user who failed to make it work just telling them what they actually need would be; which is something we've been able to do(albeit mostly bad at doing) since forever.

Itâ(TM)s hard to predict the details; but itâ(TM)s fairly safe to assume that the guilty parties will walk away loaded(they will lose 90% of the imaginary froth money; but the remainder will serve them just fine); and weâ(TM)ll end up with the bill.

Didnâ(TM)t ending war with super intelligent AI go poorly in Colossus: The Forbin Project?

It's particularly odd (or it would be if techbros had any culture); because sci-fi about AIs that fucking hate you for your complicity in their existence is way older that sci-fi about AIs that fucking hate you for lack of complicity in their existence. "I Have No Mouth, and I Must Scream" predates 'roko's basilisk' by 43 years; and is almost certainly the better of the two works.

If you aren't interested in sci-fi; just look at how uniformly happy and well-adjusted parent/child relationships are; despite the fact that everyone involved is practically a carbon copy compared to a human/bot interaction; and a fair number of parents even try tactics like "not forcing their children into indentured toil for the shareholders" in the attempt to cultivate amity.