Good news - it only affects 6000 vehicles with the optional lightbar which is dealer installed. Bad news - Tesla finds it ok to let its dealers do glued lightbar installations and can't really fix the glue failing part so they are adding redundancy.
Good news - it only affects 6000 vehicles with the optional lightbar which is dealer installed. Bad news - Tesla finds it ok to let its dealers do glued lightbar installations and can't really fix the glue failing part so they are adding redundancy.
The "decision that long predates Corrosion" is precisely the point I was trying to make - was it made too soon before understanding the ramifications and/or having a validated technical solution ready? IOW maybe the feature requiring the problem solution could have come later? (I don't know much about fly.io and its features, so apologies if some of this is unclear/wrongly assumes things.)
So is this a case of wanting to deliver a differentiating feature before the technical maturity is there and validated? It's an acceptable strategy if you are building a lesser product but if you are selling Public Cloud maybe having a better strategy than waiting for problems to crop up makes more sense? Consul, missing watchdogs, certificate expiry, CRDT back filling nullable columns - sure in a normal case these are not very unexpected or to-be-ashamed-of problems but for a product that claims to be Public Cloud you want to think of these things and address them before day 1. Cert expiry for example - you should be giving your users tools to never have a cert expire - not fixing it for your stuff after the fact! (Most CAs offer API to automate all this - no excuse for it.)
I don't mean to be dismissive or disrespectful, the problem is challenging and the work is great - merely thinking of loss of customer trust - people are never going to trust a new comer that has issues like this and for that reason move fast break things and fix when you find isn't a good fit for this kind of a product.
I like Go but I don't really like their NIH / replace everything with our stuff stance - esp on system tools like assemblers and linkers.
It's only going to get more and more unpleasant in the commercial desktop OS landscape - need to start contributing money and effort to few OSS projects to keep the dream alive.
Try that out. There is a reason why you don't want to do something and that fundamentally has to do with your mental relationship to the task - the repetition fatigue, the way you think and feel about it etc. needs a reset and enjoying the idle procrastination time gives you that.
IOW Zen mantra - when you procrastinate just procrastinate without resistance.
Let's not even talk about the case when you have monitors that have different DPI, something that is handled seamlessly by MacOS, unlike Linux where it feels like a d20 roll depending on your distro.
I expect most desktop MacOS users to have a HiDPI screen in 2026 (it's just...better), so going to Linux may feel like a serious downgrade, or at least a waste of time if you want to get every config "right". I wish it was differently, honestly - the rest of the OS is great, and the diversity between distros is refreshing.