> - harder to understand how much more is left to see
I think in this page, unlike many other scrolljacking implementations, this one is actually fully scroll-functional. ie You can drag the scrollbar from the side of your browser window, use pgup/pgdn, or click a point in the scrollbar and it still functions well, so the scrollbar gives you all the same navigation flexibility and information as a traditional page, without breaking the aesthetics.
> - interferes with the inherent perception of what the scroll does (moving a page up/down)
As for that one, I think it's evident very quickly that it moves you forward and back, unlike some other scrolljacks that try to do weird things like animate images and run slideshows and things and mixes a bunch of paradigms.
In fact, it actually felt good when I move my fingers on my scroll wheel forward and it pushes the world forward, and back when I pull back, it felt more connected than a classic up/down scroll.
As i see it, usual scrolljacking implementations give the illusion of a more immersive experience with the following tradeoffs over clicking navigation:
- interferes with the inherent perception of what the scroll does (moving a page up/down)
- harder to navigate (you have to scroll a lot to trigger a section change)
- harder to understand how much more is left to see
- harder to implement and to debug potential bugs
- needs a menu to mitigate all of the above (defeating the purpose of scrolling)
and probably more stuff that i can't think of right now