I think this headline was poorly chosen.<p>When I see the term "Open Data" I instantly think of open data portals - mostly run by governments around the world. These things have never been healthier: ten years ago they hardly existed, today you can get civic data from local governments all over the place (last time I saw an attempt to count there were over 4,000 of these portals, and that was a few years ago).<p>My favourite example is still this CSV of all 190,000+ trees in San Francisco, which is updated most business days with details of the latest tree changes: <a href="https://data.sfgov.org/City-Infrastructure/Street-Tree-List/tkzw-k3nq" rel="nofollow noreferrer">https://data.sfgov.org/City-Infrastructure/Street-Tree-List/...</a> - I track changes to it here: <a href="https://github.com/simonw/sf-tree-history/">https://github.com/simonw/sf-tree-history/</a><p>This article is about something different: it's about what I guess you could call the "Open APIs" movement. Back in the days of Web 2.0 every service was launching an open API, hoping to harness developer attention to help make the platforms more sticky. Facebook and Twitter both did incredibly well out of this strategy, at least at first.<p>THOSE APIs are mostly on the way out now. Companies realized that giving away their data for free has a lot of disadvantages.<p>Open Data is doing great. Open APIs are not.