Congratulations, now your website is a shitty experience for your users. Well done.

Javascript in the browser was a mistake. And if we had to have it, the suitable scope of it was what we had around 2004.

Google invested billions in it realizing they had a way of owning the browser space simply by making it insanely complex. Just hire all of the web standards people, tell them to go crazy and then also hire thousands of C++ browser developers for a decade to build everything. Boom, a moat!

I have a personal issue with having a 500KB page load, so a button press can be animated.

Unfortunately, it’s 1) difficult to reach consensus 2) difficult to broadcast and 3) difficult to enforce. For example, even when major browsers achieve 1) and (e.g. implement a standard component) 2) and 3) are still huge gaps.

The great things about all these crypto libraries are: - Minimal to no dependencies - Coded by security conscious people - Often externally audited

I wish more libs/deps are crafted like them. Until then the risk of rolling your own vs using a dep isn’t as different as it could be.

For those not trying to implement the dark patterns that enshittify the web.

If you don't roll your own back button behavior, you've missed the opportunity to show a few more ads.

If you don't make your window full screen on my shitty old tablet browser (yes, I'm looking at you, BBC), then it's far too easy for me to close your window. (Joke's on you, though -- my old Samsung tablet has a physical back button.)

Many eyes are supposed to make bugs shallow. In the webdev space, many eyes on something like React lead to numerous opinionated alternatives, each successful enough to warrant consideration. This doesn’t seem to be slowing down, either.

Meanwhile, vanilla HTML and DOM capabilities have never been stronger.

agreed, that page decided they needed to write their own scrolling logic and it made the page horrible.