I assume you would also have some sort of icon that indicates all of the changes you made have been synced (or the opposite, an icon for when they haven't yet).

Though of course, it doesn't help if the user outright kills the app or pulls the plug or whatever. But I think in that case they should expect to lose some data?

What's annoying is you have to do it in three steps: first transfer it to the app's internal storage, and then save it out to actual files, then delete the internal storage; and you need 2x the disk space.

(Another annoying thing is in some countries they just disable the 5 GHz WiFi, so transfers end up taking forever. Very annoying when traveling, and if I lived in one of those countries I would have definitely returned it)

Meanwhile the swifts will definitely not choose the ground.

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...

> 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?

There is a dropdown at the top-right to select the platform - no need to view source.

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?

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.

  "literal1 " + str(expression) + " literal2"

  f"literal1 {expression} literal2"

> (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

> This page is not supported. > Please visit the author’s profile on the latest version of X to view this content.

...I am using the version which their own server just served me.

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?

Profiles do have a built-in UI at about:profiles or by launching Firefox with -P, neither of which requires an extension. Admittedly this UI is a bit basic, but a better version is being rolled out (https://support.mozilla.org/en-US/kb/profile-management). Running multiple profiles side by side does indeed involve running multiple instances of the browser.

Containers are an internal API and need an extension like Multi-account Containers to provide a GUI (though this is an official extension by Mozilla), however they don't require running multiple copies of the browser.