Web developers: we are going to go out of our way to hide the scrollbars!

[rysiek@mstdn.social]

Web developers: we are going to go out of our way to hide the scrollbars!

Users: but that makes it difficult to know how much of the text is left to read!

Web developers: don't worry, we'll add a non-standard UI element that signals this in some non-obvious, weird way!

[bituur_esztreym@pouet.chapril.org]

@rysiek
yes.. we want scrollbars back! leave scrollbars alone!

[dalias@hachyderm.io]

@rysiek Spicy take: "Web developers" should not be a thing. You don't have any reason to "develop" for the web. The whole point was to factor things so that the browser and the server software were the only things that needed "development" and this development is reused by everyone. The actual documents you're publishing need writing/markup, not "development".

[lu_leipzig@troet.cafe]

@rysiek It's funny because web developers also justify using tiny npm dependencies with "not reinventing the wheel" 🫠

[th@social.v.st]

@rysiek pages are now florps. progress bar goes sideways.

[snoopy_jay@mastodon.world]

@rysiek It also makes it very difficult to scroll 😩

[notthatdelta@furry.engineer]

@rysiek Special venom in my heart for the progress bars that hang out at the top of the page, because every time I scroll down that progress bar moves and the movement pulls my eyes off the text and back to the top of the page.

0/10 UX would strike with an axe.

[libewa@chaos.social]

@dalias @rysiek
Well, there are legitimate reasons to develop applications running in the browser engine (portability as the main one).
The problem is article sites pushing advertisement bullshit into everything, and you can‘t really do that if the user just enables Reader Mode. So, make your document tree useless for everything but proprietary CSS and JS.
A web dev should just be someone developing applications for the browser engines, like iOS devs for iPhone apps.