Cache partitioning make it useless to rely on the ressource previously downloaded by another website. This means the primary benefit of shared public CDNs is no longer relevant for any modern browsers.

Other arguments:

• Security concerns
• Privacy concerns
• Reliability problems
• Performance limitations

I like the example of HaveIBeenPwned, that shows how important caching and serving resources only can be efficient.
Another solution could be IPFS, but is not production ready.

The website: https://searchatlas.org/

It shows how much the same search can prodide different results based on the country

À voir ce que cela devient. Ça semble prometteur !

Carefully chosen color palettes.

The menu "Composing a palette" and "Understanding the scale" helps

I look at the web today. Not as a programmer, but as a user of broken sites that are unable to obey the most basic rules of navigation and usability, terribly slow despite the hardware progresses. And I can only think that modern frontend development has failed.

👍
I try to do my best. But it is hard. I keep trying.

A WYSIWYG using the react code as source of thruth. It is the mix between code based and low code website generation.
It is now in Alpha.

Retour sur la panne du CDN Fastly

FLOSS of a Civilization-like game 👍

34% des sites web mondiaux passent désormais par les services de CloudFlare 😬

Et lorsque CloudFlare a un problème, 34% des sites web mondiaux ont un problème 😬 En plus des autres enjeux.

Un CDN ne délivre plus de contenu et boum.

C'est ça d'être dépendant de 93438 tiers !

Vive l'autohébergement... même si cela pose d'autres problèmes: https://shaarli.lyokolux.space/?v4bvmg

Comment rendre les services numérique inclusifs pour ces personnes ?
Question pertinente !

Actually, it is !

Thanks for this inspiring post 😄

Cet article est rempli de considérations extrêmement intéressantes sur l'intérêt qu'il y a à limiter la taille de ... tout, en fait. Mais surtout de son site web dans toutes ses dimensions : moins de features, moins de dépendances, ...
(via https://nicolas-delsaux.hd.free.fr/Shaarli/?uyqHfg)

Oh shit ! Using HTML instead of a lot of Javascript. Need to be tested.

Test the connection through WebRTC and identify the eventuals problems

Google dominates the web-browser market with Google Chrome. Now alone by itself, the company can change the rule as it wants.
Here the third cookie will be removed for good reasons; but an AI in Chrome will process the browser history to chuck the user in a similar group. Other websites will then have the obligation to integrate this changes for Google Ads, or they will have to do without 63% of the users

(via https://sebsauvage.net/links/?NNbb8w)

Calculate the size of the webpage vs the size of the screenshot of it. It can then be compared with with a bloat score (BS): WebBS = TotalPageSize / PageImageSize

OUI pour les raison déjà listés sur cette page

Le web c'était pas mieux avant car les pages étaient certes plus légères mais prenaient tellement de temps à ce charger...
Et la compatibilité s'est au final amélioré, même si ce n'est toujours pas parfait.

Le vrai problème, c’est que nos attentes ont évolué encore plus vite.