The problem is not so much that it stores state in the URL as that it uses window.history.pushState instead of window.history.replaceState.

How something functions is more important that how it is implemented.

I'll take a stateful app that doesn't break history over a stateless app that does any day of the week.

Do we really want to push the Git way of thinking onto joe-average web user.