Bufferbloat is something that seems counterintuitive at first glance. Why would adding a bigger buffer hurt performance?
Selecting appropriate buffer sizes is critical - a good set of comparisons there is what buffer would one want for streaming a movie vs a buffer for streaming a live video meeting connection.
So just in time over the oceans works precisely as intended: it gives us information immediately when there is a problem. Whether or not it's within any manufacturers power to fix those problems is a separate issue.
(And I'm going to guess that there's no easy way to fix those problems, given that Toyota has opted for more inventory to hide those sorts of transient issues when it comes to certain parts.)
Not enough people have read Len Kleinrock's wonderful books on this subject, and they are long out of print, and available only on archive.org.
I wish it were taught more. His Queue Theory volume 2 is one of the most well-thumbed books on my bookshelf.
(Money = buffered economic value; too much liquidity = bufferbloat?)
The actual issue is too much debt, alongside too concentrated money. The issue at some level is some buffers are far too big, and 70% of the US population doesn't have any buffers at all.
Here it will get lost (semi-ephemerality is imo one of the disadvantages of HN), on stackexchange people will find it.