Another very good explainer on why 'web3' is something you should stay the hell away from
Although I disagree with the ending that Yesterweb's suggested solution of harkening back to Web 1.0.
People use Web 2.0 services for a reason - not everyone wants to program their own web page.
Another, unrelated misstep that web 2 introduced was this siloing into gardens at the expense of interoperable standard media.
Those are two features of web 1 that the future does need. It's not just nostalgia. (BTW, I've been pretty happy with RSS/Atom as a solution for both these issues.)
I get, and agree with, that we want accessible publishing. That's great thing.
@Sandra I disagree with the idea that JS is something that should be avoided; static sites are hard to make; HTML and CSS are a mess and hard to debug.
I resort to JS technologies in my own work not because I want to implement trackers and nuisances, but just so the process of development is actually bearable and easy to debug.
JavaScript is an accessibilty and security obstacle that we need to employ sparingly. Last week I finally went tinfoil enough to install a JavaScript blocker. Most frustrating thing about doing that is the feeling that I should've done it s long time ago because it's pretty great.
Portable doggie solutions
@dzuk @Sandra i think a lot of the stigma around js would fall away if most bigger devs actually used it with some remorse - less trackers, and more optimization of their codebase so you dont get facebook-esque infiniloading experiences. a few examples like that from bigger platforms can sour your opinion for a technology overall
@Sandra I think interoperability would be cool, but I think the open source people who make these are their own worst enemies and are frequently creating undesirable and unfriendly systems.
I would like to believe that could change but in my almost 20 years of being online I have not seen that to be the case.