mulasien

dutchlord said:

Speed is/was never an issue with Apple devices so who cares?

Speed IS an issue if you need NVidia GPU levels of power, which the highest end Apple Silicon processors don't have. So yes, speed is an issue for those who need the top end of the scale, and there are quite a number of people who do care, even if you don't.

Edit: and for clarification's sake, I'm not referring to 'power per watt' like Apple's graphs highlight, I'm talking max power regardless of watt, of which Apple falls short.

bala1234 said:

mulasien said:

I know hating on Google is the popular thing to do on this site, but YouTube Music is actually half decent. When I was on Android, I actually used YTM as my primary music app over Spotify as I was already (and still) paying for YouTube Premium and its Supermix feature didn't have an equal on Spotify.

By contrast, I can count on two fingers the number of times I used Google Podcasts over Pocketcasts. Maybe podcasts moving to YTM will get better coverage? /shrug

I subscribe to Youtube premium (play music before that). I am also a regular user of Google Podcasts. But like you said 'hating on Google is the popular thing to do on this site'

Generally speaking for 95% of the people on this site...yes, that's accurate. You are one of the outliers 

That said, I can't disagree with you that there's a non-zero chance that Google will screw this up, so there's that as well.

I know hating on Google is the popular thing to do on this site, but YouTube Music is actually half decent. When I was on Android, I actually used YTM as my primary music app over Spotify as I was already (and still) paying for YouTube Premium and its Supermix feature didn't have an equal on Spotify.

By contrast, I can count on two fingers the number of times I used Google Podcasts over Pocketcasts. Maybe podcasts moving to YTM will get better coverage? /shrug

StrangeDays said:

mulasien said:

But...why though? What problem is this solving that's not going to introduce bigger problems?

FTA you just read: "But it would also potentially give the iPhone 15 Pro greater water and dust resistance"

What problems does your engineering background indicate this will introduce?

First issue has nothing to do with engineering, but rather a user adjustment from the last 10+ years of interacting with an iphone. The ability to mute your phone by feel and know if it's muted without having to look at a screen to confirm via a toggle switch. One thing I missed when I was on Android phones was that physical toggle. Having to go into settings to mute my Android phone was a PAIN vs simply toggling a physical switch. Losing a toggle switch after establishing it as a differentiating feature of iPhones feels like a step backwards, in my opinion. That is a user-interface trade off to be made in favor of better water resistance, though I'd wager that the current water resistance is just fine now without having to make such a major trade off.

From an engineering standpoint, if the buttons are haptic only, how do you hard reset the phone in the case of a lock up? If the buttons are software-driven, and the software is inoperable, what's the manual bypass?

The only thing more non-user-friendly would be to remove the charging port...or are you part of THAT crowd?

But...why though? What problem is this solving that's not going to introduce bigger problems?