You can think it as a cross platform networking library.
From the post.
"Low-level networking improvements like HTTP/2, QUIC, QUIC to TCP failover, gRPC, DNS replacements, push/streaming, observability, analytics, state of the art TLS, retry and timeout policies, etc. take a tremendous amount of effort both to implement robustly as well as to make consistent across all of the Android and iOS versions in common use. Envoy Mobile will provide all of this functionality in a consistent cross-platform manner, especially when paired with Envoy running at the edge, similar to how server-side Envoy provides consistency to polyglot distributed application architectures."
Yeah I think the idea is, envoy helps a lot on the server side, but the client side uses almost the exact same algorithms, so we ought to have something like envoy on the client side too.
This can work, but stacking framework on top of the framework is what made the classic application servers undesirable and a horrible mess to begin with.
Observing similar patterns creeping in the Kubernetes culture and ecosystem does not inspire optimism in a side observer like myself.
I really wish everyone had a chance to use the autopilot feature and judge themselves. I use it every single day and trust the machine.
Issue is, with every complex system, there are few ins and outs that users need to know - like lane merge buffer lines, sharp lane merges by another vehicle in front of view, etc. Within your first few rides(below 10), users could pretty much guess when it works and when it might have issues.
On labeling the feature, it is marked clearly BETA and wiggle prompt is shown pretty much in all the confusing cases - so alert is never missed for me.
My only gripe is with all these incidents, Tesla is forced to update the feature to make it less user friendly or take out completely. I genuinely feel safe and come home every single day with less stress. Elon's tantrums are not helping the situation either.
Blaming the users doesn’t seem like a winning strategy. If the system needs users “guessing” about its behavior maybe it should be gates behind a test with periodic checkpoints as the software behavior changes.
I have been using AP2 every day for more than a year now as its very convenient but inherently dangerous as its addictive and provides a false sense of security as it works great ~ 90-95% of the time. I would not be opposed to an auto-steer ban to force Tesla to get their priorities straight about stationery object detection and auto-braking and stop scamming people about their self-driving if its really years away. You can still use adaptive cruise which eases all the commute hassles yet forces you to be actively engaged.
can i ask why you “trust” the system with your life so much?
there’s not a single piece of software i trust in my daily life. i mean, something as simple as an iPad, phone, computer, tv, etc. hardly goes a day without a glitch, but yet people are ready to trust “self-driving” auto features as if they’ve never experienced a software failure before. and normally, it isn’t a software failure in the strictest sense. it’s a human error embedded in software. so i ask myself, do i trust the however many overworked, sleep deprived, wide-eyed engineers’ abstract and concrete thought now embedded in cars’ active driving systems? the answer is no way.
There is a huge difference between Adaptive Cruise Control and regular Cruise Control. I agree completely with you on Cruise Control, however with adaptive, stress level is low there is no comparison. I use it pretty much every single day in my commute.
Yeah it's not a big recall in the scheme of things but it is a major percentage of the total production of the Model S (wikipedia says they were up to 212,000 at end of 2017).
GM's big ignition switch recall was 800,000, Firestone recalled the tires for millions vehicles back around 2000.
Most automakers sell millions and millions of units in a short period of time, but Tesla does not. I’d be more interested to see what percentage of Tesla’s have been subject to recalls vs the total shipped, and compare that to a similar mainstream metric.
I thought that seemed really high, so I did a little looking and horrifically it’s actually a bit lower than the industry average of 46%! Some of that is skewed by VW recalling more cars in a year than it sells in a year, but still...
As a dad, my killer app on Google Home is playing youtube audio/video. Alexa can't match it. Then almost all the integrations I care are already available on Google Home - Smarthings and Nest.
I tried multiple times playing Alexa, it doesn't come close to Google Home's voice recognition capabilities.
Agree. More like some kind of a monotonic presentation rather an educational one. Books are great for reference though. If you had a choice, just buy all the books and skip one day session.
There were few questions about the experience. Though job description has quite a bit of experience mentioned, we are open in considering a good candidate with relevant skill set.
From the post.
"Low-level networking improvements like HTTP/2, QUIC, QUIC to TCP failover, gRPC, DNS replacements, push/streaming, observability, analytics, state of the art TLS, retry and timeout policies, etc. take a tremendous amount of effort both to implement robustly as well as to make consistent across all of the Android and iOS versions in common use. Envoy Mobile will provide all of this functionality in a consistent cross-platform manner, especially when paired with Envoy running at the edge, similar to how server-side Envoy provides consistency to polyglot distributed application architectures."