LLMs are just so antithetical to the way Apple works and makes products. They are first and foremost control freaks over the content they present as "From iPhone" or "From Apple". I would be absolutely shocked if they ever one day took content from a non-deterministic black box and presented it directly to the user. They have always human-curated nearly everything user-facing that comes from their products, and entered into partnerships for content grudgingly and always with a plan to control the content vertically once they are able to. The big exception obviously is web search, but I can only imagine how much it pains them to not have an iron-fist control over the search results on Safari. They'll never embrace an AI content roulette wheel.
> I would be absolutely shocked if they ever one day took content from a non-deterministic black box and presented it directly to the user
Aren't the notification summaries just that? When they came out there were lots of examples of their horrifying results (summarizing Messages threads to sound like family members died etc)
> I do think the challenge for Apple going forwards (but also for Android) is going to be how to best take advantage of AI.
IMO one of their great advantages so far is that they have not blindly bought into the AI hysteria and wasted $billions on it. They've shown you can still have a great company without chanting the "AI is the future" mantra day in and day out. It would be pretty disappointing for a new CEO to drag them into the cargo cult and declare "We, too, must find something that we can do with AI."
You can’t compare Apple to any other company. Apple is the only successful consumer hardware company (with Samsung being a distant second). They can afford to sit out the AI arms race.
You can’t be a software company without an AI story to tell.
Honestly, I'm pretty bullish on Apple and AI. I think there move is in local, open source models. These are getting better and better for generic ChatGPT—type tasks. I'm kind of waiting for Apple to ship their own Ollama. And it's going to be a huge win for both them and consumers.
I don't see selling local LLM servers/software, as such, being something that makes sense for Apple, but selling an "Apple Intelligence" appliance that works with your Apple devices and/or provides home automation might do.
I just think the concept of an LLM is counter to how Apple treats content on their products. See [1] for more of my thoughts here. I think the only chance Apple embraces AI is if they manage to research a 1. local model that 2. is purely deterministic, whose output can be reliably constrained and controlled by Apple.
> IMO one of their great advantages so far is that they have not blindly bought into the AI hysteria and wasted $billions on it.
They both bought into hysteria and they've likely already wasted billions on it. Are you forgetting the interminable ads and announcements of "Apple Intelligence" from two years ago when even iPhones were marketed as AI-ready?
Knowing the literature is criminally underrated. Nobody even asks for it anymore. I used to ask candidates when was the last time you implemented something described in a paper or textbook, and walk me through how you did it, and after 2010 or so, people stopped even being able to come up with an answer. I've worked with junior developers who get stumped with basic things like what units or format for arguments to pass to some SDK provided function, and they try everything besides reading the official SDK docs.
I hear you, but I still feel for the coworker, and if I newly joined a company and learned on my first day that they are failing the Joel Test[1] here in 2026, I would get that sinking feeling in my stomach that I made a huge mistake. There is no longer a valid excuse for having a build like that. "It's documented..." and "Nobody wants to touch..." "Not worth it to..." "Can't justify..." are all huge red flags.
Nice list, somehow I missed that one. I love Joel's wisdom.
The full build literally works in one step but the main prerequisite is to perform a few git clone commands which can be copy/pasted from the readme. Can't help it if they want to manually do git clone and let it name folders incorrectly and then subsequently ignore compiler errors and my advice to rename. Changing our antiquated workflow would have required changing a lot of other sensitive dependencies. What ever happened to the old adage "never change a running system" ? ;)
And people here are concentrating on our build system, which I will be the first to admit isn't perfect, but this isn't the only instance of me telling this person how to do things, them not listening to me and doing something else, letting me debug only to realize they didn't listen, telling them how to fix, only to be ignored _again_, rinse and repeat. It's unfortunately a recurring theme. I initially thought it was a communication error on my part, but I've heard similar complaints from several other colleagues as well.
See, you are probably right about that new hire. But the way you say things here, you do come across (at least to me) as "that guy". You know? "That guy" that says "we've always done it this way and that is why it's good and why we still do it that way".
What happened to "never change a running system" is that if the system is barely running at all, you better do change that system.
If I'm the new guy and you tell me how to do things and those things seem bad and there's no explanation for why they need to be that way, I'll also ignore you, coz I know how I want to do things and how things can be done better. Don't tell me to do things X way. Many roads lead to Rome and some are better than others. See my other reply. At my very first job I was also told how things work and how to do things. But things sucked and so I made them better anyhow.
Now, in the other part of the thread you also did mention how they just sent you error logs without reading and thinking about them themselves and such. That definitely is a red flag and the kind of thing that will make me fail someone's probation period. Definitely. But just because someone doesn't think that "the way we've always done things" is a good reason to keep doing something bonkers is where I'm no longer with you. And again, probably just your wording/what you disclose in various parts of these threads but it explains why "we concentrate on certain things only" ;)
> "That guy" that says "we've always done it this way
I most definitely am not, and constantly push back for changing processes, and do make changes when I am allowed, even when it's not budgeted for or even officially allowed, because we have legacy systems that need to be maintained and some things are truly outdated and need some love. In fact, as a new hire in another life, I used to get scolded for changing _too much_ because I like to constantly improve things. The problem is, in order to ship code at our company and within our budget constraints, you don't have time to constantly refactor, unfortunately.
> is that if the system is barely running at all
Our system is and has been running just fine for many years, thank you very much :)
> there's no explanation for why they need to be that way
There is an explanation: There is no shell script because there is no root for all the repos, and some repos are shared across multiple projects.
I hate reiterating this yet again but is it really that hard to copy/paste a couple git commands? The readme is quite short, and once you've done it one time, it's fairly easy and straightforward to understand.
This is like saying Winner Take All Capitalism doesn't have an exclusionary mechanism for the rich. The system exists for the sole purpose of serving the already-rich. The vampires are an inevitability baked into the system from the start.
The folks fighting perpetual copyright were not fighting to make it possible for Disney to fire creatives. In fact they were fighting for the creatives to triumph over Disney.
Disney is all in because all their characters are entering the public domain over the next 5 years. They can't fight like it's 1998 because youtube is now worth more than they are.
> In fact they were fighting for the creatives to triumph over Disney.
We were doing nothing of the sort. It was "Information wants to be free" not "we want to provide a perpetual job for a subset white collar workers".
Well I was in that cohort and none of us were thinking we were helping megacorps create the content slop machine from 1984.
Our concern was that corporations were expanding the definition of intellectual property to the extent where you couldn't make a movie or song or write a book as an individual without some corporation with a massive "IP" warchest coming after you and declaring it derivative. You couldn't write some software without a corporation with a massive repository of junk patents claiming you infringe.
We wanted to insure that individual creators could continue to have a voice, and not get sued out of existence by an IP Legal/Industrial Complex that was forming causing arms races between megacorps and SLAPs against everyone else.
If we knew we were feeding a yet-to-be-invented slop machine that would allow megacorps to unemploy all the creatives, most of us would not have supported that.
And by the way Disney is all in on AI for the same reason they were all in on perpetual copyright. In the perpetual copyright world, having a massive library of content you no longer have to pay residuals on was a source of massive amounts of "free" revenue. You could just keep re-releasing and re-making stuff. You did not have to do the messy, expensive work of paying people to come up with really good new stuff.
In the AI world, the money-printing capital asset is the trained model that grinds out slop 24/7 and you -emdash- again -emdash- don't have to pay actual people to create anything new.
>If we knew we were feeding a yet-to-be-invented slop machine that would allow megacorps to unemploy all the creatives, most of us would not have supported that.
We have multiple Communist ais that is on par with Western ai from 18 months ago and can run locally on 5 year old hardware.
I have no idea the fever nightmare you live in but the future is bright and only getting better.
I think you just want to make a comparison of copyright to slavery.
Property classes are born and die everyday. You can own the rights to publish an arcade video game, but that class of rights would have been way more valuable 45 years ago. NFTs were born and died just recently. You can own digital assets worth real money in an online game that simply shuts down.
Some people may read this and say "these don't qualify as a property class", to which I will remind you that property class used in this way is a brand new term, which I think is invented solely to be able to compare the limitations on human freedom associated with slavery to the limitations on human freedom associated with intellectual property.
> The last time a property class was removed was _slaves_.
Easy counterexample: titles of nobility. Also perpetual bonds, delegated taxation rights, the ability to mint currency. The list goes on.
If you're going to use history to support your AI bull agenda, you should at least pre-fly it with the AI first -- it would have pointed this out.
> Arguing that copyright is good because a subset of big tech doesn't want it around is as stupid as arguing that slavery is good because the robber barons don't like it.
Sorry, who's saying it's good? You are, actually, insofar as you're willing to support the right of AI companies to take people's information and use it to create copyrighted model weights. Why do you care less about the intellectual property of billionaires than that of the common man? Do you really think they're on your side?
What's more likely to happen is that humanity won't go totally extinct--it will just drastically shrink. When robotics and AI perform all useful work and everything is owned by the top 1000 richest people, there will be no more economic purpose for the remaining 7,999,999,000 of us. The earth will become a pleasure resort for O(1000) people being served by automation.
> Using my Mac or Windows PC, it's very rare that I actually want an app to access files on its own that it didn't create. Like if I write a doc in Word, I'm only going to edit it in Word. I might want to email a copy to someone, but that doesn't mean Mail needs RW access to the original.
I think this depends on your definition of an app. When I write a text file in vim, I definitely want grep and sed and awk to have access to it. When I edit a source code document with VSCode, I want Python to be able to read and interpret it. To me, the core of computing is documents that are passed along from app to app, gaining value at each step.
vim, grep, sed, and awk would need to inherit permissions from the shell for this kind of sandboxing to be reasonable there, maybe on account of being child processes. I wouldn't want to sacrifice any usability there, I do everything in CLIs.
This isn't even just an Apple attitude. The whole macOS and iOS software ecosystem has this "nothing before the prior two OS releases exists anymore" attitude, and it is absolutely infuriating. It is absolutely possible and not a huge lift to support prior operating systems, but Mac developers just don't tend to care or do it.
The reasonable way to go about hardware deprecation is to not do it until that hardware is Truly Gone™, buy some actual definition of Gone that isn't an arbitrary number of years or versions.
I don't even think it's about partisan tilt anymore. This administration's M.O. is raw chaos, havoc, and just this low-level randomized churn that keeps us all conditioned to believe that nothing in government works deterministically anymore.
reply