by super_linear on 11/12/23, 10:21 PM with 41 comments
by friend_and_foe on 11/13/23, 6:55 AM
by doublerabbit on 11/13/23, 12:22 AM
"Up to the cloud"
There is no need for a car to "up to the cloud". Just give me a local Bluetooth network that reports back to me engine ECU reports, statistical logistical reports and driver stats. Because as soon as you leave the ground to "reach the cloud" that's where open-source stops.
by jauntywundrkind on 11/13/23, 2:49 AM
Since it's not named in the title it's: Eclipse UProtocol. Protobuf & CloudEvents. Url-based, with different devices ("UDevice") each getting their own dns name ("UDomain"). Somewhat transport agnostic. Http2, amqp, mqtt, dds (used some in ROS robotics os).
This makes me rather miss Webinos, which was a connected is with pretty interesting end user privacy systems kind of built in that let the device kr car talk to a cloud, but a user defined cloud.
by bastard_op on 11/13/23, 12:49 AM
Why? Auto vendors realized they lost control through their ineptitude of the user interface, and want it back. Problem is no one wants what they have to offer, that is a sub-par experience in every way to simply letting them use their phone as a screen in their car already there.
Automobile vendors realized they screwed up and lost real estate while they were still screwing with Microsoft, Clarion, all the other WinCE vendors and few others longer than they should, and are simply going to piss everyone off trying to take it back again.
by jauntywundrkind on 11/13/23, 2:47 AM
Since it's not named in the title it's: Eclipse UProtocol. Protobuf & CloudEvents. Url-based, with different devices ("UDevice") each getting their own dns name ("UDomain"). Somewhat transport agnostic. Http2, amqp, mqtt, dds (used some in ROS robotics os).