Earlier quoted context omitted.
"Google had the best search engine, it became a centre of gravity..." Almost no one made serious attempts at competing with Google. And not because of network effects or any other hard blocker. In the early 2000s, the industry just wasn't mature enough to heavily fund serious competition. By the 2020s the industry has funding and founders ready to jump on any huge opportunity that presents itself. There are of course…
Microsoft had a good go with Bing.
Apple's accidental moat: How the "AI Loser" may end up winning
391–400 of 402 posts
Re: Apple's accidental moat: How the "AI Loser" may end up winning
#392Gemma4 in my view is good enough to do things similar to Gemini 2.5 flash, meaning if I point it code and ask for help and there is a problem with the code it’ll answer correctly in terms of suggestions but it’s not great at using all tools or one shooting things that require a lot of context or “expert knowledge” If a couple more iterations of this, say gemma6 is as good as current opus and runs completely locally o…
Looking at current advancements - this is the horse I would bet my money on.
Re: Apple's accidental moat: How the "AI Loser" may end up winning
#393Earlier quoted context omitted.
Apple's Neural Engine and the CoreML framework to leverage it are almost a decade old now. Apple Intelligence was a rebrand, and Apple has made some unique decisions rolling it out. For instance, the new chatbot version of Siri's hallucinations were seen as unacceptable, so its release was delayed. Is a chatbot that provides false information regularly really an advancement? Apple chose not to do photorealistic gener…
That is definitely true, but some time ago Apple’s marketing team has also put out some pretty cringey commercials to the contrary. It’s wild how they seemed to be encouraging people to cheat and hide their ineptitudes, rather than just being honest about it.
Hell, there are chatbots out there trying to convince kids that suicide is a great idea.
How is prioritizing pushing out slop as quickly as possible with no consideration of the consequences acceptable?
Re: Apple's accidental moat: How the "AI Loser" may end up winning
#394Earlier quoted context omitted.
It has an excellent reputation of having no reported accidents!
My regular tow truck driver tells me he sees all sorts; fords, audis, mercedes, teslas, even the odd exotic car like a lambo - but never once an apple car would you believe it.
Re: Apple's accidental moat: How the "AI Loser" may end up winning
#395Earlier quoted context omitted.
We're not talking about writing assembly by hand here. If your software has a million daily users and wastes a minute of their day, that's about 9 work-years of labour wasted every single day. In a 5-year lifecycle that's about 10,000 years of human labour wasted. Yes, I had to quadruple-check this myself. Does it take 10,000 work-years of effort, per project, to train its developers to write reasonably performant co…
What world are you living in where the median piece of software has a million users? Or even a hundredth of that?
Unfortunately the number of users and the collective value of their wasted time doesn’t make arguing for efficiency and performance any easier.
Re: Apple's accidental moat: How the "AI Loser" may end up winning
#396Gemma4 in my view is good enough to do things similar to Gemini 2.5 flash, meaning if I point it code and ask for help and there is a problem with the code it’ll answer correctly in terms of suggestions but it’s not great at using all tools or one shooting things that require a lot of context or “expert knowledge” If a couple more iterations of this, say gemma6 is as good as current opus and runs completely locally o…
> That’s a problem.
While improvements should continue rolling in, and might even match current SOTA in benchmarks down the line, is it "good enough"?
Hard to believe we have reached that stage with current models, which would continue to stretch beyond what we can economically run. Call it skill issue, or try to fix it with a revolutionary harness, it seemingly takes a village to get it all working. Maybe by then we will have good enough ecosystem in these layers too, but if current capabilities is the benchmark, it might need more time in the oven.
Re: Apple's accidental moat: How the "AI Loser" may end up winning
#397if hardware moat was to be discussed, then compare with nvidia, amd and google's tpu division perhaps. in-house intelligence is best left alone for apple. they are relying on the "peers" for underlying capabilities as is. [1] [2]
outside of inference and (pro/con)sumer space, there is little to offer for the enterprise or the people developing the lowest end of the stack. even the recent tinygrad egpu is shockingly slow [3]. which might made gb10 look much more capable for in-house training.
regardless, most of the industry "moat" does not appear sustainable at best. only time will tell how it will turn out for everyone but on a positive note, apple does not put all its eggs in this basket, which is probably wiser.
[1] https://news.ycombinator.com/item?id=40636980
Re: Apple's accidental moat: How the "AI Loser" may end up winning
#398Re: Apple's accidental moat: How the "AI Loser" may end up winning
#399Earlier quoted context omitted.
We're not talking about writing assembly by hand here. If your software has a million daily users and wastes a minute of their day, that's about 9 work-years of labour wasted every single day. In a 5-year lifecycle that's about 10,000 years of human labour wasted. Yes, I had to quadruple-check this myself. Does it take 10,000 work-years of effort, per project, to train its developers to write reasonably performant co…
What world are you living in where the median piece of software has a million users? Or even a hundredth of that?
I once noticed my name in the Chromium OS credits due to a patch I had submitted to a library that's on every Chromebook. 1 million would be a small number for Chromebooks alone.
Re: Apple's accidental moat: How the "AI Loser" may end up winning
#400Earlier quoted context omitted.
Local models seem somewhere between 9 and 24 months behind. I'm not saying I won't be impressed with what online models will be able to do in two years, but I'm pretty satisfied with the prediction that I won't really need them in a couple of years.
We still aren't going to be putting 200gb ram on a phone in a couple years to run those local models.