Here's one way: there's not a singular axis that users wanting sync and users not wanting sync can be placed on and compared.
The other poster expressed how the feature sucked for their purposes. But the feature wasn't made to punish them, it was made after evaluating the preferences of many users, which is what my question is getting at.
Features can introduce risks in various ways. I discovered this long ago through a software vendor's annual feature request solicitation, in which I learned to be ware of what others ask for: you may get it.
Specifically as to sync: I would love to be able to sync certain elements of browser state between my systems.
Not between one of my systems, some arbitrary third party of questionable trust and intentions, and another of my systems. But directly between my systems.
Google actively thwart this.
A feature of most early browsers was the ability to save bookmarks to a file, and import that elsewhere. By slight extension, a browser session or tab state can be saved, either directly, or as bookmarks.
Chrome does not do this, either at all, or on all platforms. It's most resistant to this on the consumption-only platform of Android.
This has been a major point of frustration to me for a year and a half as I've been wanting to dump user state from one system to another, without Google intermediating that exchange for me. I've found no means of accomplishing this.
That is one element of the tyranny of the minimum viable user, as well as of Google cattle-prodding its users into the feed chutes.
