Thing about most of those no-JS solutions is that you sacrifice user experience for the sake of avoiding JS. In this case we're sacrificing user controls, which is a massive part of the UX. In a more feature-complete CSS slider such as csslider, you sacrifice modularity, semantics and (usually) filesize.
Taking another example from youmightnotneedjs.com, the image switcher is a massive UX nightmare. Try switching image a few times, and then clicking the back button a few times. Not very fun to be trapped on a site because you have to go back through the 20 times you switched image. Could be fixed by switching to a <input type="radio" />-based system, but that just goes to show that it takes some thinking to do correctly - and then we're back to modularity, semantics, etc...
Need to know how to enable it? Go here.