Yeah, P30D as presumably intuitive to non-technical users has me chuckling

Also, knowing that TODAY > signup + P30D transpiles to TODAY > signup + 30.days in Ruby. Which one is more readable?

Point taken. Will see what I can do.

Probably TODAY + Duration({ days: 30 }) would be a better example then.

Is this even valid ruby? Doesn't it need Rails-specific Active Support to work?

The double-tap gesture is something I was very excited about and have completely forgotten about since getting my watch. The caveats around what it takes to activate it (screen activated and facing vertically) are just so great, you wonder if anyone at Apple actually tried this and found it to be a better alternative to interacting with the screen. Their demo video actually does a perfect job of capturing just how ridiculously theatrical you have to be to get it to work: https://support.apple.com/guide/watch/use-double-tap-for-com...

I was also excited about it, until I tried it and discovered it has pretty poor usability. It's not always clear what the double tap will do. Maybe it will scroll, maybe it will clear the item you are looking at, and maybe it won't do anything.

About the only thing I use it for is stopping a timer - it’s great for that.

Always wonder why companies see suing people as a better course of action than hiring them.

That’s the bummer for me. The primary place I’d like to use this is surfing. Too much time to think, and too few practical ways to record those thoughts.

“Sweden-like gang shootings” is not a phrase I expected to come across

First thing I did was check https://nissan.com which apparently I haven’t done in years. RIP Uzi!

If it really was a red line, why did Steve even take the meeting, and then take days to decide on it?

Wired CarPlay FTW

Implementation still varies between car to car. Example: Mach-e interrupts the song playing and takes many seconds before it resumes. Sometimes this leads to multiple driving instructions preventing the song from resuming for a long time.

Other implementations (looking at you Hyundai) crash requiring you to pull over, disconnect the phone, reboot the infotainment and then re-enter your navigation destination.

The best implementation is no carplay: instead use an AUX port and mount the phone on the dash.

Second best is Tesla's custom navigation. They do something other car companies should: use one of the million speakers in the car to focus on navigation directions while allowing audio content to continue playing on all the other speakers. Such a simple idea but so good.

My phone is much smaller and harder to read than my car's screen. Also, my phone overheats when I'm driving in the hot sun, which causes it to dim the screen. I've had a dash-mounted phone for many years; Carplay has been much better for me (though yes, it has occasionally crashed).

> ...use one of the million speakers in the car to focus on navigation directions while allowing audio content to continue playing on all the other speakers.

My previous-gen Kia Sedona does this as well (at least when using the built-in maps).

I’ve spent a lot of time with both, and hands down the wired one is far more flakey. Granted I think that’s more a Mazda software issue, but a solid 10% of the time I get “CarPlay failed” and the only way to fix it is to turn the car on and off. Never once had an issue with wireless in a Hyundai.

In my Mazda the wired CarPlay also seems to fail a lot. But whenever I rent a car with wireless CarPlay it's been fine. Take this one anecdote for what it's worth.

My Mazda’s wired carplay has never once failed so…take this one anecdote for what it’s worth.

Have you tried cleaning out the lint in your phone's port? For me, that was it and my Mazda CX-5 connects fine every single time after I did that.

I assume you mean you went iStats -> stats

Also not comparable to UUIDv7 because it isn't sortable