One interesting reason there's a been a bunch of progress in this space is that automotive systems are required to show the rear view camera in a certain amount of time. Progress driven by the oddest of things.
My car takes around 10 seconds(I think more im not sure) for the reverse camera to work after starting the engine.
Its annoying having to wait, thats for sure
I've been deep in the interview cycle lately and I just had a dream last night that I was asked, in a non-technical interview with a product manager, "what are the 5 ways to dockerize an application?"
I then said that I could only think of one way, and he responded "how do you not know docker if you are applying for a java developer job?"
well most of the time, my company deals with docker aswell.
but my coworkers have nothing to do with it, it just is fully automated.
the only problem we had, when introducing long running jobs that can be run while clicking a button inside our ui, which runs a k8s job.
that was hairy for my coworker, but with enough shell scripts it started to be easier and easier.
That's cool :) I mean, it's fine to not know the answer to everything. Usually it's not a deal breaker, especially if you provide a general answer of "here's how i tHink it works"
But what's always hilarious to me is 3 seconds after they ask the docker question, they'll then ask "ok so tell me a bit more about how CompleteableFutures, Consumers, and Threadpools work together and why you would want to use them"
or my personal favorite, the predictable trifecta of
"whats the difference between an abstract class and an interface"
"ok tell me how garbage collection works"
"ok and whats the difference between final, finalize, and finally?"
The rear view camera system almost always runs independent of the main Head Unit (HU) or In-Vehicle Infotainment (IVI). In most cases the rear view camera view is a single application specifically coded for the target micro processor (SuperH for example) and is the only thing running on that micro processor. The HU and the rear view camera share the display. While you are driving in R the HU is booting Linux or QNX and when you move to D the screen switches to the HU. The rear view camera application keeps running uninterrupted.
What you said is/used to be right but GP is also probably right, hardware companies love to migrate distributed and reliable system into overcomplicated but integrated Linux contraptions
Why not just wire the Linux box to the car battery? Most after market dash cams do this to capture accidents during parking. Certainly a low power device is enough ?
You would be surprised how even the most innocuous electrical systems can draw down a car battery if the car doesn't move for extended periods, especially in cold weather and with a battery that's already degraded or only gets charge from short drives.
I have an old car (with a modern <2 year old battery BTW) sitting in the driveway that rarely gets driven. For a long time, every time I wanted to drive the car the battery charge would be so low it would fail to crank the engine enough to start it. I would jump-start it and drive it for at least an hour, and if I would drive it again within a week or two it would be fine, but after ~3 to ~4 weeks the battery would be dead again.
When I finally got around to diagnose the problem and measured leak current while removing the fuses 1-by-1, I found out that the tiny light in the glovebox compartment was not turning off because the lid switch did not engage properly. The current was something like 100 mAh but it was apparently enough to drain a less-than-full battery within only a few weeks...
But that makes sense, right? 0,1 Amps = 2,4 amps/day, many cars have a ~60 Ah battery, so that would be empty in 25 days (and probably in less than that doesn't have enough power to start the engine).