bhauer

> but is this actually addressing a real threat?

US Executive Orders 14110 and 14141 did create fairly onerous regulatory regimes that could have constrained the dynamism of the marketplace. However, my understanding is that both have been rescinded, so they do not currently post a real threat.

Yes, it is performative. As is most of the outrage in this thread.

Apple is undeserving of its popular reputation as a leader in user interface. The article points out only a sampling of the egregious human interface issues with Apple software and devices. Whether it's iOS, CarPlay, or any other Apple software, they're all dramatically overrated. The trouble is, many of the alternatives are even worse. Android? Also awful. Most OEM infotainment systems? Even worse than CarPlay. I feel Apple is well-regarded simply because it's the lesser among several bad options.

We need a viable third option in mobile operating systems. At least with cars, we have high-quality infotainment systems such as those from Tesla and Rivian. In the mobile phone space, we have tow poor options and a few alternatives with vanishingly small market share.

> Light mode might be annoying to read in no-light environments, but dark mode is nigh impossible to read in high-light environments.

Backlit screens are difficult to read in high-light environments regardless of whether you're reading black text on white or white text on black. I use white-on-black ("dark mode") on my e-ink Kindle to read outside all the time. And the same is true on our Daylight computer. White-on-black remains my preference in high-light environments.

I switched to T-Mobile at the last upgrade interval because of this. My family looks forward to no longer relying on Garmin InReach devices when out hiking.

Same. That's the beauty of automatic thermostats. They target the temperature you specify automatically. So you specify your favorite temperature once and never interact with them again.

I guess everyone is different, but what you described absolutely doesn't resonate with me. I never have adjusted my HVAC vents after their initial configuration. Winter, summer, whatever. I always want the air to flow the same way.

Software lag isn't unique to touchscreens. Software lag is always a terrible thing, and developers who de-prioritize performance should be ashamed, but that is true regardless of what input is used.

> Yes I do prefer analog controls. Dials for heat. Open close flaps for vents. On off switches.

Dials and switches can be fully digital (e.g., dials can be free-spinning, without locks at each end of a setting). So preferring dials and switches seems reasonable. But flaps for vents are very difficult to automate. Returning to manual flaps in cars would mean losing modern cars' ability to associate and restore HVAC vent preferences with driver profiles. It would mean returning to the time when it was actually necessary to adjust the HVAC vents every time you swapped drivers. While setting vent preferences on the screen may take a second or two longer than manually setting them, thanks to the setting being associated with my driver profile, it's a set-once-and-forget-forever setting. The net time and annoyance savings is large.

Previously, it seemed the sliding sync required a Postgres-backed Synapse installation. Does the Matrix 2.0 version of Synapse provide a seamless upgrade path for those using the default Sqlite installation?

Correct take. But I also want to point out that this earnest reply is casting "remove curse" on this cursed library.

> prioritizing some pretty little visual animation over actual functionality

This describes iOS in a nutshell.

The step-up in cost basis on death is the original sin that underpins the entire debate over unrealized gains.

It's disheartening to see so much thought and deliberation going into an obviously toxic idea (taxing unrealized gains) when the obvious solution (removing the cost basis step-up when assets change hands) is being ignored.

Inherited wealth is the least earned, so it should be politically palatable to change this. But presumably because such a change would acutely affect the people who make laws in the country specifically, it is never seriously considered.

Agreed. Explicitness and comments are very useful in understanding the intended functionality and logic, whether or not the code actually implements that intent correctly (an in providing that intent, they can help identify bugs earlier than they would be identified otherwise).