Yes, we are talking about manufacturers.

A manufacturer of processors wants good evaluation boards to be available, since this can drive sales of the processor.

If you get a school to use the evaluation boards (because the board and examples holds good quality) then you get a lot of new workers who will look for this processor when it gets time to design own solutions.

If company A buys evaluation tools for three different processors, and the evaluation board + examples holds good quality and quickly shows that the processor A can solve a problem, then evaluated processor B and C will be dropped in the waste bin.

If manufacturer A creates a new processor, that isn't 100% identical to a previous processor (not likely that only power consumption or form factor would have changed), it is likely that the manufacturer wants an evaluation board for this processor too. And example code too. Good coding practices for the example code for processor A will reduce the cost of creating example code for processor B. And will improve the probability that the examples will work and make the buyer happy.

A quick availability of a high-quality evaluation board with high-quality examples will lead to a faster decision process, making new customers select this new processor for their products.

In the end, MANUFACTURERS should really care a lot about the quality of their examples. It is their bottom line that gets hurt by bad examples. A really stupid manufacturer may have a great processor but never manage to survive because no one will care about the processor.