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.
10,326 karma · joined January 12, 2012
Personal Application Omnipresence (PAO): http://tiamat.tsotech.com/pao
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.
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.
[1] https://tiamat.tsotech.com/pao (2012)
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.
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.
This describes iOS in a nutshell.
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.
While that is the overall conversation, this specific subthread is rooted on a comment suggesting a world without marketing wholesale.
It's funny. Here in the United States, I find houses with bull-nosed interior walls discomfiting. Something about all the rounded corners causes me mild distress. I find it much more comfortable being in houses with sharp-edged meetings of walls.
The Mercedes system will absolutely not follow navigation routes, change lanes, execute right and left turns, execute U-turns, stop at traffic controls, and so on. All of which FSD will do.
A broadly capable Level 2 system that is suitable for 99% of driving scenarios (with supervision) is way more interesting than a tightly constrained Level 3 system that is only suitable for <1% of driving scenarios.
Would a Level 3 system that only navigates parking lots at up to 5 MPH be notable versus a Level 2 system that drove everywhere? For me, a very narrow Level 3 system like Mercedes' is absolutely less interesting versus a very broad Level 2 system like Tesla's. The technical capability of Tesla's system is substantial. How important is taking liability, really, to the bigger picture of increasing the technical capability of autonomy? A narrow Level 3 system is not an entirely empty milestone, of course, but compared to the actual work of increasing driving capability, assuming liability seems like a game played primarily by deploying lawyers, not programmers.
It's remarkable how often these significant limitations are ignored.
The difference between SAE Level 3 versus Level 2 is liability, not functionality. Conceptually, it would be relatively simple to create a Level 3 system that only worked in parking lots and never drove over 5 MPH. And yes, such a system would be "Level 3," which naively sounds better than "Level 2" because the number is higher.
But you could compare such a system that works only in parking lots against Tesla's Supervised FSD Level 2 system which controls the vehicle at prevailing speeds on all city streets and highways, executes left and right turns, stops at traffic controls, executes U-turns, parks, and everything else. Tesla doesn't want to assume liability yet because they are still iterating fast. The last few builds have been released about two weeks apart.
The functional domain of a Level 2 system can be significantly greater than a Level 3 system. And that is the case when comparing Tesla Supervised FSD versus Mercedes Drivepilot. It remains commendable for Mercedes to take on liability, but we should not kid ourselves. Doing so is a play for cheap media wins and punchy-sounding milestones like what we see in this article. It's not actually moving autonomy forward in any meaningful way when compared alongside Waymo and Tesla FSD. The scope of the Mercedes system is simply too narrow.
That said, the ST keyboards were notoriously squishy, lacking much in the way of tactile feedback. So many people didn't particularly enjoy them for touch-typing.
No. It has always been awful.
I was briefly excited to hear that media synchronization had been separated from iTunes. That gave me hope that I would be able to put media on my phone without a cloud intermediary and without the crippling mess of iTunes. But, sadly, my experience is that the Apple Devices App simply doesn't recognize my phone at all, so it's non-functional for me.
First, the linked documentation provides no information about where to get the Apple Devices App. It turns out, it's only available from the Microsoft App Store. Fair enough, but odd that the documentation never says that. Second concern: yikes, this synchronization app is 188 Mb in size. But whatever, I have tons of storage on my PC, so let's proceed.
The final and biggest issue: the app simply never recognizes my phone. The phone is unlocked and has trusted the computer. It shows up in Windows Explorer as a storage device (significantly hobbled by Apple's needless file system obfuscation, but that's not new). The Apple Devices App never stops saying "Connect a device to proceed."
All told, a typical Apple software experience.
If Android weren't so awful, I'd be much happier. The way Android devices appear as just a standard storage device with a normal file system is so much easier to deal with.