As a long-time OSM contributor (former editing software maintainer, former OSM Foundation board member yadda yadda) I like this piece, because it actually gets the "mutual aid" dynamic between corporate OSM and enthusiast OSM.
The two should not be opposed. Rather, the more people are exposed to OSM via Facebook, Apple and so on, the more enthusiast contributors OSM gets. The more rendering tech that Mapbox releases as open source, the more opportunities OSM enthusiasts have to build cool stuff. And so on.
We get a fair amount of sniffiness from some of the more corporate types, denigrating enthusiast contributions as just early-stages stuff that should now inevitably give way to AI-assisted machine mapping. So to read a more balanced view like this is genuinely refreshing.
_But_ it does require both sides to understand the bargain and play fair, and that doesn't happen as universally as I'd like. There are some among the enthusiast community who are unremittingly hostile to corporate actors beyond what anyone should have to put up with, salaried or not. To some degree that's inevitable when you have a project that attracts single-minded 15-year old Linux geeks, maybe, but that explains rather than excuses.
Conversely, corporate OSM too often acts in its short-term interests without a view to the wider good. Attribution is the most notorious example, where Facebook, among others, is basically flouting OSM's attribution requirements. This breaks the "more eyeballs, more contributors" compact. We also see it where corporate editors steamroller some of the nuance from individual contributors' edits (particularly logistics-driven), and I'll confess I'm not a great fan of Mapbox's recent decision to close the source of the dominant in-app renderer, though that's clearly their right to choose.
If this thoughtful article helps both "sides" realise that they're better working together than against each other, that would be a win.