Marco Arment

And it's just, you know, it's terrible.

Setting aside, that's probably not what Apple's problem is.

Their problem seems to be just with the basic AI stuff or whatever.

But yeah, I would, you know, this is the type of thing where like if you keep making a mistake in one direction, you keep overcooking something.

Just try to undercook it.

Just try to undercook it once.

Like go in the other direction because people like correct for it and they're like, oh, we're going too far to A. We need to go to B. And they go like slightly less far to A. And it's like, can you at least make a mistake in the other direction?

And, you know, the mistake in the other direction of being like, you know, Snow Leopard, no new features or whatever.

Let's actually do this as a marketing push.

And that was kind of a one-time thing.

So I think they need to massively correct currently in the direction of shoring up existing functionality, which is exactly the opposite of what Marker was saying.

It's like, you just got to ignore stuff because you're behind that AI.

But like, I think those two things are not mutually exclusive.

And that gets to the second point here, which is, would you change to a 1.5 or 2-year cycle or whatever?

I have said for years and continue to say, based on my 25 years experience in the software industry and releasing products on schedules and deadlines, that it is absolutely possible to have annual releases by smartly choosing what goes in those releases or not.

You can stagger them.

You can have two-year plans, three-year plans.

It's not like, oh, you can only do things that fit in one year.

No.

This is a scheduling possibility.