Not only that, Safari also started to partition web cache in 2013, and it's still the only browser with such partitioning. [2] Without it, tracking doesnt even need cookies.
"If you only block cookies, you still have all the other storage and stateful things to worry about." - Safari ITP engineer John Wilander [3]
Also the spin of the article is slightly dishonest, simply turning off third-party cookies in Chrome achieves to negate most of the explicit criticism in the article. The author probably had the conclusion of the article in mind (setting up good Firefox against evil Chrome) before looking for supporting arguments.
It's a bit ironic. While mainstream media starts to discover the existence of third-party cookies, which had been a known issue for around 20 years, Big Tech tracking has already moved to first-party tracking, fingerpringing and cache tracking.
For example, Facebook switched to first-party cookie tracking in 2018. [4]
Everyone who wants to understand the dynamic needs to look into the relationship between Apple and ad tech, with Apple's recent counter-move being the addition of ITP 2.2. [5]
Since the release of ITP 2.1, even first-party cookies now are limited to 7 days, and all first-party cookies that are even potentially tracking cookies get deleted after already 1 day. [6]
Firefox doesn't play much of a role in this fight. In fact, Firefox never did anything pro-actively to make ad-tech sweat. The decision by Mozilla to block all third-party cookies in 2013 [7] was reverted in fear of Ad-Tech.
Mozilla is better at marketing than with the technology, and still hasn't enabled tracking-protection except for new users.
[1] https://twitter.com/brendaneich/status/982631777574338561
[2] https://twitter.com/johnwilander/status/1126191449161158657
[3] https://twitter.com/johnwilander/status/1126208457214836736
[4] https://www.adweek.com/programmatic/the-facebook-pixel-will-...
[5] https://webkit.org/blog/8828/intelligent-tracking-prevention...
[6] https://webkit.org/blog/8613/intelligent-tracking-prevention...
[7] https://blog.mozilla.org/netpolicy/2013/02/25/firefox-gettin...