Comments by "Comm0ut" (@Comm0ut) on "When EV makers go bankrupt, what happens to the car?" video.

  1. That's legally impractical because modern software uses proprietary COMPONENTS unrelated to the company fielding the APPLICATION. If you code X which is then incorporated in Y application whose corporate owner goes bankrupt what is the justification to NULLIFY your intellectual property? FOSS advocates cannot even agree on a universal license format.
    1
  2. It becomes parts for enterprising enthusiasts. The solution for new buyers is simple. Never buy low volume vehicles from weak companies. Always wait several years then buy what is proven in FLEET use AND loved or at least liked by mechanics. I don't buy computers without checking what the community thinks of their repairability (no Applol for me) nor vehicles. When I want to know something about a machine I ask people at my or higher skill level (I'm a lifelong mechanic and techie but no one knows everything and wise humans seek out wiser humans!). Companies using proprietary code often cannot choose to release it or the source so that puppy is (at present) dead in the basket. What could be required is full SELF-diagnostics to be required for all vehicle systems. There is no reason data extant already for system operation should not be available for BIT (Built In Test) use. Everything every onboard computer "sees" should be available to the operator, displayed both onboard and via OBD connector. The vast majority of automotive electrical work is what we called "swaptronics" in the Air Force. Replace parts in question per mfrs fault tree (plus practical experience) then BIT and operational check to verify repair. I and my avionicsbros prefer fixing combat aircraft to working on cars because aircraft are designed with maintainability in mind while cars continually get worse. Thanks for all you do and keep up the good fight!
    1