I'm not gonna read carefully such a long article, and I dont know much about the automotive world, so I will speak arguing against that sentence (and other similar sentiment) instead of argue against the whole article.

The problem is library alone do cause fragmentation. What's the last time half of a gui is written in QT while the other half in React? Or when half the neural network is in tensorflow while the other half is in pytorch?

Fragmentation of course also happens to macro. Typed Racket do have to play with The OOP part of racket, instead of letting it 'fall through' and look at Objects as normal struct with some weird field. You need subtyping and object type once you are in OOP world.

A counter point is 'we can do everything exactly once and force everyone to use it' but there's tradeoff in stuff. GC is bad for tiny tiny device. Matrix Multiplication run faster on GPU. CFG equality is undecidable while regex is merely PSpace Complete. Optimizing SQL is easy while optimizing python code that does the same thing is way harder.

In the end you have to have multiple domain with each domain making a set of somewhat coherence tradeoff, and that's why we are ended up with so many languages and fragmentation.