"Natively" as in 2 lines of CSS rather than yet another JS dependency. The cool thinks about CSS Snap Points is that they fall back rather gracefully on brothers that don't support them to just standard overflow scrolling.

Well that's not what native means. Beyond that, the issue isn't that Safari is not implementing HTML5 features fast enough, it's that they are choosing to not implement specific ones in order to protect their platform. You just don't see that from other browser vendors (today)

Isn't that the point of this article? I don't think it's fair to criticize Apple for lagging HTML5 support in iOS, then say "what's the use of this element?" when it cuts the other way.

The criticism isn't that they are lagging HTML5 support in iOS(although it would be valid- that's no reason to sue), it's that they are specifically avoiding parts of the implementation to protect their platform. Things like full screen support, notifications, etc