It's mentioned in the article, the real problem was they kept trying to contact remote support to "verify" the light was out. Leading to a backlog of requests which they couldn't get through fast enough.
My only * to this would be Google Chromecast devices directly if you already have them.
They have an option (buried way under settings) to make the home-screen apps only.
> Turn on Apps only mode
> From the Google TV home screen, select Settings Settings and then Accounts & Sign In.
> Select your profile and then Apps only mode and then Turn on.
It also makes the device significantly more performant.
> I ride their robotaxis daily and see them performing better than Waymo, but it's obviously meaningless until we see accident stats after they remove safety monitors.
I've seen this claimed a lot but never have gotten a definitive answer.
Is this like "overall better but hard to pinpoint" or "this maneuver is smoother than Waymo" or something in between?
Would love to hear experiences with them since they're so limited currently.
Yeah Tesla has more smoothing, but IMO that's less interesting than the ability to navigate tricky scenarios and model other actors. Here's my collection of interesting videos, Tesla only because those are the ones I get forwarded to me. I'd love to see a similar collection for Waymo.
Smoother maneuvers, or things like seamlessly backing up a bit when it predicts that a large vehicle turning from an intersecting street won't have enough room to turn unless the car moves out of its way. It's really cool.
IMO the implementation (for me at least) is ... terrible. Why reach for this when it's, at the end of the day, just the exact same as NDK work in C++ but in Swift.
You have to use Kotlin / Other UI setup anyways (or their fully-native example, use OpenGL to draw the screen[0]), and on top of that statically assign the package path and class name in the Swift code, while making it an external func in the kotlin code[1]. You then also get to deal with the annoyances that come up with native libs.
kotlin side:
/*
* A native method that is implemented by the 'helloswift' native library,
* which is packaged with this application.
*/
external fun stringFromSwift(): String
swift side:
@_cdecl("Java_org_example_helloswift_MainActivity_stringFromSwift")
It's worth pointing out that the example you linked with the cdecl is not showcasing the swift-java interoperability but using "raw" JNI patterns as if you would do it with C.
cough un-ecrypted experian backups getting stolen from a UPS truck at gun-point and nothing else stolen cough
reply