#Choose where smoothscroll goes code

These drawbacks are often also true of many libraries that deal with scroll behaviors, whether that’s parallax effects, or other scroll-coupled animations. Having a library to do smooth scrolling is going to be something that has to be kept up-to-date and maintained, and it will add to the overall page weight of the site.

#Choose where smoothscroll goes code

More maintenance for developers, more code for users to download.

That’s not necessarily a disaster, depending on what else the page is doing, but if there is some long-running work on the main thread, and scrolling has been coupled to the main thread, the net result can be stuttering scrolls and jank. As with any JavaScript added to the page, there will be an increased CPU load. Increased propensity for main thread contention and jank.So while the motion may be smooth it can feel wrong or uncanny. Secondly, the library’s smoothness physics won’t necessarily match those of the platform’s. This manifests itself in two ways: firstly, one site may have a smooth scroll behavior, but another may not, so the user can end up feeling disoriented by the inconsistency. There are downsides to both libraries and extensions that change scrolling, though: Users also do this, too, through extensions. The solution to the stepped native, input-driven scroll behavior for many developers has been to use libraries, the goal of which being to remap it to something smoother and nicer on the eyes.