Live data from Hacker News

iOS 27, iPadOS 27, and macOS 27

apple.com

221–230 of 373 posts

Re: iOS 27, iPadOS 27, and macOS 27

#221

Earlier quoted context omitted.

I personally use the swiping keyboard on ios and it seems to detect the wrong word with an almost malicious frequency. It also randomly Capitalizes things.

For some reason, the one word that it just will not let me swipe is “and”. Which is, you know, somewhat common. I get all kinds of random things instead.

and -> Abe for me for some reason.

Re: iOS 27, iPadOS 27, and macOS 27

#222

Earlier quoted context omitted.

Any improvements to voice to text? I use iPhone 13 Mini and so keyboard has always been hard to type on. But voice to text..man..it is an absolutly miserable experience that I wish I could swap out for any other competitor. I normally don't complain that iOS/MacOS isn't customizable because the defaults are good enough to work for me but that voice to text man its like they completely forgot about it.

There is also a new, larger voice to text model available... but not for an old iPhone like the 13 mini. Only like the iPhone 17 Pro and above. The best workaround is a third party app that lets you run Parakeet V3 or Whisper on your phone. There are quite a few.

It’s by far the best speech to text I’ve ever used so I’m a fan

Re: iOS 27, iPadOS 27, and macOS 27

#224

So, is it better (faster, stronger, etc) than iOS 18? Everyone says iOS 26 was not good at all and iOS 27 is much better, but it seems like it's fairly simple to make something that's better than iOS 26. A more interesting question is whether it's better than iOS 18? Does anyone have any experience switching from iOS 18 to, say, some beta of iOS 27?

It improves performance on the oldest iOS device that is supported.

Compared to iOS 18? Or just compared to 26? how so?

Re: iOS 27, iPadOS 27, and macOS 27

#225

I love Siri's suggestions for categories in my shopping list. At the moment it puts "Dishwasher Rinse Aid" in the "Beverages" category.

Well, the kids were eating Tide Pods not too long ago, seems like Siri's not that inaccurate after all.

That was almost 10 years ago. Seems like it was just yesterday.

Re: iOS 27, iPadOS 27, and macOS 27

#226

I love Siri's suggestions for categories in my shopping list. At the moment it puts "Dishwasher Rinse Aid" in the "Beverages" category.

Well, the kids were eating Tide Pods not too long ago, seems like Siri's not that inaccurate after all.

From what I recall, the only people actually eating Tide pods were elderly folks with dementia. The kids were joking about it a lot, though.

Re: iOS 27, iPadOS 27, and macOS 27

#227

Earlier quoted context omitted.

On Safari I use - Wipr (Ad Blocker) - 1Password (Password Manager) - Dark Mode HN (HN dark mode hack.) Not really sure what else I need tbh

Just a heads up, you can have dark mode on every website on iOS Safari with Dark Reader: https://darkreader.org/

I use Dark Reader on Chrome, Edge, and Firefox, but I've found Noir to be better on Safari.

Re: iOS 27, iPadOS 27, and macOS 27

#228
post #101
post #41

People who are still on Chrome as main browser should seriously try Safari 27. Compatibility greatly improved, super speedy. Although for some reason the AI organise tab option is not showing up on me.

Does uBlock Origin (or something equivalent) work in Safari?

AdGuard as well.

Re: iOS 27, iPadOS 27, and macOS 27

#229
post #11

Reminder to wait a couple of months before upgrading macOS! Every single time issues are found after a new macOS version, give it a little bit of time before jumping right away on your work machine :)

You do you. I backup and install once the RC goes live. Have done for years. Only problem I recall was a few years ago Homebrew got in a tizzy for a day. One exception maybe is for music producers. For some reason AU/VST/DAW developers don't seem to take part in the beta programs and their software can take a while to get updated. But I've happily been playing with Bitwig (with some Arturia VSTs) over the weekend on…

I keep the studio computer OS a full version behind.

My impression from audio developers is that the audio infrastructure is very badly documented (like so much of MacOS nowadays) and using it properly requires a combination of luck, WWDC videos, and devrel threads. Also, Apple introduces changes that are genuine improvements in theory, but break undocumented assumptions.

The lack of rigor is a bit surprising given that audio is probably the only mission-critical hard-real-time thing MacOS does. People routinely run an entire live concert on a Mac and an audio glitch is not OK! (Yes, if it’s Taylor Swift budget then there are at least two machines in sync with a big red button to switch over…)

But given what they’re dealing with, I understand why it’s more involved than just “the developers didn’t try the betas”.

Post reply on HN