The readings will have an extremely low signal to noise ratio, at best you coils differentiate a truck from car by length of the pulse, but with speed already being ±30% variability any small difference in cars inherent properties (size in length or amount of metal) would quickly be reduced to nothing. Then for every make and model you have thousands of cars already, I don’t see how you could possibly differentiate between those even in theory.

I can really appreciate the performance is (should) be the same, makes a lot of sense

Gtk 3->4 made a lot of internal changes, and at least some were related to making wayland work. Wayland “worked” in gtk3, however it was very much an afterthought, and half the toolkit was useless under wayland. Other changes are usually required for changes related to rendering, gtk4 had vulcan rendering which may require some breaking changes. Another thing is just general breaking changes that are good, sometimes you realise some decision was bad, and a new major release is just a way to make these.

From the end users perspective nothing much changes, it maybe looks a bit different, but not much besides that. But a vulcan renderer and being fully wayland compatible are major improvements that also improve the user experience, even if you don’t notice directly.

It doesn’t, it’s just a “solution” to make cars “better” without fixing anything. But some people think that “if we just make cafs cars better” they will eventually become good

Yes please, let’s fix cars so we can have more cars because cars good! If only cars didn’t have as much emission