He means the 600+ trains …
For me, it looks more like that the train has already sailed. The support nightmare of over 600 Linux distributions can no longer be controlled.
About 30 years ago, there was another need to unify Unix. AT&T System V, BSD and Xenix became System V Rel 4. This made it possible to create compatibility, especially on the source code level. All manufacturers changed over then to this version. This had advantages. With Linux, standardization is only half-baked lip service. Things like file system standards can't hide the fact that the distributions are extremely diverse, and manual pages also have no real quality. Compared to the BSD-based systems, a difference like day and night. But it is also logical, who can document something in detail for all systems, if you cannot guarantee that for example paths or other things are not really the same everywhere. So, it's better to leave it out, but that's not good documentation.
Furthermore, I don't know any other Unix, where in some Linux distributions the mailx doesn't support attachments cleanly (and this in 2022, decades later since mailx exists…), so I had to use the mutt for scripting the other day. Or that AWK scripts, which are properly written and run on FreeBSD under Linux, simply deliver different results, which costs you hours of work because you first think you have made a mistake. In short, I find the code quality lags that of commercial Unixes and *BSD. But no wonder, with 600 distributions, many cooks spoil the broth. Everyone keeps making the same mistakes instead of working together with many hands to create something great.
Standardization and more quality is required, but if you tell this to the people, nobody understands …
UFX+, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1650v4, Win10Pro22H2, Cub12Pro