To my knowledge, 1Blocker uses the iOS/macOS content blocking APIs, which essentially allow an app to provide lists of content to block to the system, which pre-computes a fast/efficient ruleset for use while browsing. This results in lower energy usage, faster browsing, and more privacy during browsing.

Chrome does not to my knowledge provide an API like this, and extensions are still roughly a JS bundle that defines blocking rules at runtime, slowly, using more energy, and potentially having access to your browser history while it does it.

The posted article is all about how the changes Apple made to Safari mirror the proposed changes to Chrome. Safari content blockers such as 1Blocker are pretty much exactly how Chrome adblockers will work in the future.

Chrome has not changed how extensions work yet. That's all in the future. Currently, nothing has been turned off and the "old" mechanism still works. Eventually that will change, just as Safari has already done.