I guess that's Rosetta 2, and TFA is referring to Rosetta 1.
But don't worry, Rosetta 2 is also on the chopping block:
> Rosetta was designed to make the transition to Apple silicon easier, and we plan to make it available for the next two major macOS releases – through macOS 27 – as a general-purpose tool for Intel apps to help developers complete the migration of their apps. Beyond this timeframe, we will keep a subset of Rosetta functionality aimed at supporting older unmaintained gaming titles, that rely on Intel-based frameworks.
> A few places where we still help, even after iOS 27 ships:
> Google Wallet. Create a Pass is iPhone-only. Roughly half of the wallet-using world is on Android, and our generator builds Google Wallet passes from the same form.
What does this actually mean? Google Wallet has had a button to add your own passes for many years. How is the feature described here different?
I switched to Android for a year last year and moving back to iOS was really painful. A lot of things make so much more sense in Android. I really miss being able to manage notifications granularly directly from the notifications for example, or quickly copy/paste many previous things from my clipboard directly from the keyboard, but what I miss the most is the AI integration, using AI is so painful on iOS
I have another list of issues with Android, but the killer was how good iOS battery and how good iPhones are as physical products. But I miss a lot of things on Android now too (like the folding screen)
I made the mistake of switching to an iPhone 17 from an S24. The phone had a problem so I thought why not try the famous UX of iOS? I had issues but I found the solution.
I barely look at notifications anymore, it’s useless, does not group by app, can’t take any actions from there. Even if you open the app, the notification remains, so it’s just clutter at this point.
Clipboard does not exist.
Chrome sometimes when opened, opens up the address bar and there is no close button, I need to navigate away from the page I was on, or refresh. So I switched to safari, good job google.
The biggest annoyance would be the back button or rather the lack of it. Every app does it somewhere different. It could be a left swipe in some apps, a back button on top left, a tick box on top right. There is no mental model you can rely on.
Then I realized I am using it wrong. iPhones were never made for people like you or me. We just wants to finish our work as soon as possible. We zoom through multiple apps and get things done. iOS is for toddlers/old people and technologically challenged crowd. We need to think like them.
So I treat the notification shade just like other users, glance and ignore. No need to manage it or clear it.
Clipboard are needed when you copy multiple things. That’s because you want to paste multiple things. You are trying to do too much at the same time. Think of the most “simplest” person you know, they wouldn’t do what you’re doing. So I stopped doing that.
Back button was only an annoyance when I either used non-apple apps or do things fast. Again doing things fast is not what your simple friend would do. They would take time and each action, press, swipe would be deliberate, not careful yet confused.
Basically stop trying to be a smart person while using an iPhone. You might be a wizard in front of a terminal. iOS is designed for a large and specific set of audience and I truly respect Apple for catering to them. Most corporations like Google or Microsoft will try to teach their users and make them something they are not. Apple accepts them as they are.
This comment has a lot of grammar mistakes which I am frankly not going to fix. The apple keyboard is terrible to go in between words and sentences to edit them. But the target audience would never do it anyway and Apple proudly supports their decision by not improving the keyboard. I think that’s a noble thing to do.
On mobile they’ve hidden that under “customize this article”, which I never would have even noticed if I hadn’t specifically known that there is some sort of dropdown somewhere, heh. But now we know :)
Is this part true? The article's fix involves running a command and rebooting the computer. If restarting the app was sufficient, surely you wouldn't need the command/reboot?
I guess not. Looks like if you choose the Documents directory once, you give your implicit permission to the app until you choose another restricted directory.
> It's incredible that about 80% of people in this thread seem to be commenting without having looked at the website.
In defence of the 80%, there is no indication in any section other than the About page that it is not real money (with the possible exception of the suspiciously high sums of money), and most commercial services have fairly useless About pages. The HN headline presents it as if it's real.
A far cry from GP's implication that "inadvertently click[ing] on the website" is sufficient to see this.
Can you spoil it for me, because I read it to the end and saw no mention of such a project. Unless you are referring to the DIY approach the article suggests.
The answer is linked to by the section of the article you quoted:
> (1) If you statically link against an LGPLed library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application.
And also answered directly in the section you quoted:
> as long as you provide the object files and allow users to relink your app with a different version of Qt
>> What I mean is you can’t just look at a board and know the ko “state” - but yes I’m sure in practice it’s not that important.
> Chess also has this "problem" thanks to rules like castling and en passant capture.
Chess is intended to be stateful. If you forget whether a castle has occurred (and then the king walked back to its starting position, and a rook repositioned into the corner) or not, chess players will note that you've messed up the game. The castling rule is there to stop you from castling more than once.
Go is not intended to be stateful, and if you forget that a particular board layout may have come up in the past, go players will not note that you've messed up the game. It doesn't matter. The ko rule isn't there to stop you from repeating a board twice. It's there to stop you from having to repeat a board layout an infinite number of times, because things like the need for food and sleep would interfere with the game.
Wrt the implementation concern, this distinction means, for example, that you must always track the castling state regardless of whether a player asks for it, whereas you're fine not bothering to track the history of a go board unless a player asks for it. You can just say "if you want to invoke ko, press this button, and we'll remember that board layout, and if it's already been flagged, the game will draw". That isn't done, but it could be done.
I'm not a Go player so I don't really know how it works in practice, but what you are saying seems to disagree with the wording in Wikipedia, so I'm curious which one is correct?
You say:
> if you forget that a particular board layout may have come up in the past, go players will not note that you've messed up the game. It doesn't matter. The ko rule isn't there to stop you from repeating a board twice.
Wikipedia says:
> Rule 8. A play is illegal if it would have the effect (after all steps of the play have been completed) of creating a position that has occurred previously in the game.
> Consequence (ko rule). One may not play in such a way as to recreate the board position following one's previous move.
> While its purpose is similar to that of the threefold repetition rule of Western chess, it differs from it significantly in nature; the superko rule bans moves that would cause repetition, whereas Western chess allows such moves as one method of forcing a draw.
To me that sounds like you do need to track this, in both chess and in Go, though for different reasons (to force a draw vs to prevent an illegal move). Is this not enforced in practice?
But don't worry, Rosetta 2 is also on the chopping block:
> Rosetta was designed to make the transition to Apple silicon easier, and we plan to make it available for the next two major macOS releases – through macOS 27 – as a general-purpose tool for Intel apps to help developers complete the migration of their apps. Beyond this timeframe, we will keep a subset of Rosetta functionality aimed at supporting older unmaintained gaming titles, that rely on Intel-based frameworks.
https://developer.apple.com/documentation/apple-silicon/abou...
reply