Live data from Hacker News

iOS 27, iPadOS 27, and macOS 27

apple.com

831–840 of 884 posts

Re: iOS 27, iPadOS 27, and macOS 27

#831
post #504

This is going to sound like a really weird and irrelevant nitpick, but I dislike how they changed the version numbers to be year+1. I like that they all unified and have a relationship to the current year, but we're not buying cars. We're getting operating systems and not being confused about chronology is pretty important for bug tracking or other minutiae. Plus, the Mac lineup use(d) the year of release. Why move a…

As someone who has been doing iOS programming for ~16 years I'm glad they did something. Nothing better than running Xcode 16, on macOS 15, to do iOS 18 work. Unless, of course, you also have watchOS 11 work too.

Re: iOS 27, iPadOS 27, and macOS 27

#832

My favourite feature about this release is that support for ultra wide monitors dramatically improved. I bought a MacBook Pro (M5 Pro) in march and was shocked that it did not work properly with my LG 38WN95C-W Monitor (3840x1600@144Hz via USB-C). This has been fixed with macOS 27. I finally can use the native resolution + HiDPI with my monitor.

Oh! How's the text rendering now? In macOS 26 I had to return a new ultrawide because macOS hates non-retina displays and text was blurry af. Worth trying now?

I got a MacBook a few weeks ago, first Apple computer I have ever owned. I was so surprised when I plugged my 4K monitor into it, there didn't seem to be a way to run it at native resolution and all the text was aliased.

Re: iOS 27, iPadOS 27, and macOS 27

#833

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?

For me 26 absolutely chews through battery compared to 18 (I have the last gen iPhone SE). Hopefully 27 doesn't make that worse, but i'm holding off on upgrading. Really took me by surprise.

Definitely made it worse for me. I'm on 15 pro, and when I have anything intensive open (ranging from youtube video ~ games), the phone starts burning through my hand and the battery in it. I would've kept 18 forever, except the camera on the old one died out and replacement came with 26 :(

Re: iOS 27, iPadOS 27, and macOS 27

#834

I've been using it for several months since the developer beta came out; overall I'm extremely positive on it. One of their better releases that seemingly focused more on quality and refinements than new-features. Siri is definitely worth using now, even if it remains still a work-in-progress/needs continued refinement. It can surprise you in good ways, but it isn't consistently good yet. The keyboard remains unfixed…

> Siri is definitely worth using now

Just tried it this morning after my shower:

- Siri, what's the weather like?

- I don't know where you are

- ... use the the geolocation??

- You need to unlock first

So yeah, still unusable to me even for the most basic shit

Re: iOS 27, iPadOS 27, and macOS 27

#835

Earlier quoted context omitted.

How is the keyboard broken? Maybe I'm so used to whatever it is that I'm blind to it.

Try an android keyboard and go back to an iphone. Having switched back and forth between both systems it’s quite remarkable how bad the iphone keyboard is. In practice , typing on an iphone means constant typos, bad autofix, and bad suggestions.

Completely agree. I switched from Android to iOS... 6 years ago now? and the keyboard immediately felt off. I thought it was just something related to needing to adjust, but I reused my old Android (Pixel 3a) for the first time a few days ago (cuz I'm working on an Android app and wanted to try it on an actual phone) and the keyboard just works. No typo, no ass completions, I can actually type fast as I feel it and the text ends up mostly (99%) correct on the first try. On iOS I sometimes really struggle writing exactly what I want (the worst offending situation is iOS "correcting" a word when I hit send, so what's sent is literally not what I typed)

Re: iOS 27, iPadOS 27, and macOS 27

#836
post #291

Earlier quoted context omitted.

How is the keyboard broken? Maybe I'm so used to whatever it is that I'm blind to it.

I know the autocorrect is broken -- I consistently hit a bottom row character like "n" instead of spacebar, and it's simply unable to comprehend that you might have hit a letter instead of space. It comes up with all kinds of insane, implausible suggestions for the autocorrect, but never the obvious one that's 1 character from what i typed.

Oooh that's what's happening! I sometimes end up with garbage like "so ' I'll" instead of, say, "someone" and I wondered how it happened.

Re: iOS 27, iPadOS 27, and macOS 27

#837

Earlier quoted context omitted.

How is the keyboard broken? Maybe I'm so used to whatever it is that I'm blind to it.

I have an English/Italian bilingual keyboard set up as my default. Every single f**n time I begin a sentence with "È" (Italian for "she/he/it is") - which is an extremely deliberate gesture - you have to keep the E tapped until the accents pop up - it will immediately correct it back to an unaccented "E". It's nuts. There is a metric ton of intent behind my selecting, keeping tapped, waiting for the accents, picking…

I have French / English and every time I start my sentence with "The" (obviously the start of an English sentence), it autocorrects as "Thé" (tea). There's veeeery few situations in French where a sentence can start with "Thé".

Re: iOS 27, iPadOS 27, and macOS 27

#838

Earlier quoted context omitted.

That's a nice overview, but it seems to compare iOS 27 to iOS 26. Isn't iOS 26 known to be terrible, though? I'd like a comparison to a "known-good" iOS version. Basically I skipped iOS 26 (so I have zero experience with it) and am now wondering whether iOS 27 is any good

> The good news is there are some places where things are just better across the board. In general, iOS 27 feels peppy. I know, we always talk about snappiness, but given the time Apple has spent on improving performance and removing bugs with this release, it’s reassuring to see that it’s borne out by my experience. Apps launch quickly, photos sync faster via iCloud, AirDrop transfers are especially rapid, browsing…

[dead]

Re: iOS 27, iPadOS 27, and macOS 27

#839

Earlier quoted context omitted.

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

> The good news is there are some places where things are just better across the board. In general, iOS 27 feels peppy. I know, we always talk about snappiness, but given the time Apple has spent on improving performance and removing bugs with this release, it’s reassuring to see that it’s borne out by my experience. Apps launch quickly, photos sync faster via iCloud, AirDrop transfers are especially rapid, browsing…

I didn't see a single reference to iOS 18 in that article. So while I understand it would be faster than 26, those of us wondering about the comparison to iOS 18 are still in the dark.

Re: iOS 27, iPadOS 27, and macOS 27

#840

Earlier quoted context omitted.

It’s so much worse than that. This happens to me on a daily basis with both MacOS and iOS. Say I’m searching for Chess, I’ll get to the C-H and it’ll show the Chess app, but enter that next -E and it’s totally gone. It feels like the system is designed like “Well, I showed them Chess when they entered CH, but they kept typing, so they must not actually want Chess.” This ends up breaking for me like 95% of the time, a…

> I’ll get to the C-H and it’ll show the Chess app, but enter that next -E and it’s totally gone It "works" exactly the same on Windows. How is that even possible?

It's probably asynchronous reranking doing something weird. My guess is that the underlying ranking algorithms in these desktop search bars are very ropey, and they can't debug or diagnose because privacy reasons means the developers don't get to see what results were generated for different query/index combos. Also search is probably just not staffed most of the time.
Post reply on HN