I know he didn't explain his position in details, so a 1800-word article sounds a little unfair, but I think dry and sharp statements need adequate context and analysis.
@MaxArt2501@simevidas Sorry, re-reading this and realizing what you're asking. Payloads of that size are very common with React apps. Do they need that much? Of course not. But it would mean rebuilding them without React.
And back to my original point: a lot of that HTML doesn't and shouldn't require JS at all. JS is in fact the problem.
@cferdinandi@MaxArt2501@simevidas I think Massimo is generally making the point that some web sites require JS for core activities, not as a design choice, but out of technical necessity. (My own example: media player). Once you accept that JS is required on a site, you make different decisions about web component design. Designing WCs so there’s a noJS fallback - as you promote, Chris - is a valid choice, it’s just not the only sensible choice.
🤔 I really want to figure out how to make #FediThready be able to post to a Mastodon server WITHOUT requiring a back-end.
I'm pretty sure it's possible to do OAuth and store the token locally without one, but i would love it if someone could point me to an example of this rather than figuring it out from first principles.
@domhabersack that’s a neat little trick! I’m not too bothered by the message, but it’s good to know there’s a way to turn it off if that ever changes. 😊
On s'occupe de la partie serveur du site de loterie à partir de 10h30 sur ma chaîne #Twitch. Codage en #PHP maintenant que la partie #HTML/#CSS et #JavaScript est bouclée.
Hier j'ai fait un peu de #JS, ce ne fut pas si laborieux que ça. Voici comment seront choisis les numéros de ticket de loterie par les participants : https://youtu.be/vdTp7XzNmBE