Wouldn't you have the same issue at the next light, and still be stuck waiting to turn, making no forward progress at all?
Note that I'm assuming an unprotected left turn (with right hand traffic as in the US) at a busy intersection with incoming cars running yellow lights; please let me know if any part of my assumption mismatches yours.
My understanding is that the Motorola trackers have UWB but phone support isn't widespread yet. I haven't looked deep enough to see if that satisfied your other criteria though.
That would be hard to do with Google intentionally sandbagging things like YouTube (I'm thinking about them using a nonstandard version of web components, plus a super slow shim for Firefox, instead of using the standardized version that Chrome also supported).
Yep, not that many top-tier talent in the US willing to be in the factory for the graveyard shift under high pressure. The lines run 24/7 and if anything is slightly wrong techs need to be already on site to go fix it, because it's crap tons of money for every second of downtime. That leads to a corporate culture where even R&D has similar pressures from your boss (because essentially you're always racing with the competing fabs).
Ive never understood this culture. This kind of operation could be achieved by having several teams of folks working in shifts so noone is working crazy long, no? It seems like the company is unwilling to invest in the manpower required to achieve that SLA? fwiw ive heard similar things about the fruit company.
They have 24/7 people on site, 4 shifts that cover the work...but those are generally techs in the US, which have associate degrees or less. In Taiwan they are generally engineers that work the 24/7 shifts.
I believe that's usually so they can track when a library has a security vulnerability and needs to be updated, regardless of whether the upstream package itself has a version that uses the fixed library.
You can kind of see this in golang. Originally it came with stuff to download dependencies, but it had major issues with more complex projects and some community-made tools became popular instead. But it meant that multiple tools were used in different places and it was kind of a mess. Later on a new system was done in the default toolchain and even though it has problems it's good enough that it's now surprising for somebody to use non-default tools.
I've done the blank import thing before, it was kinda awkward but not _that_ bad.
reply