And for what? Again - there is a swath of use cases which would be hard without React and which aren’t complicated enough to push beyond React’s limits. But there are also a lot of problems for which I can’t see any concrete benefit to using React. Those are things like blogs, shopping-cart-websites, mostly-CRUD-and-forms-websites. For these things, all of the fancy optimizations are optimizations to get you closer to the performance you would’ve gotten if you just hadn’t used so much technology.

The issue with most slow JAMstack sites is that they load a loooot of JavaScript. Remember that any added JavaScript has to be sent to the browser, which will also need more computation for it. It quickly impacts performance.

Web Performance and Web Performance Optimization are still valid and descriptive terms for our industry, but we might benefit from a change to our language when working with others. The language we use could be critical to the success of making the web a faster and more accessible place.

It would seem that, realistically, the benefits of Brotli over Gzip are slight.
[…]
if you’re faced with the prospect of weeks of engineering, test, and deployment efforts to get Brotli live, don’t panic too much—just make sure you have Gzip on everything that you can compress (that includes your .ico and .ttf files, if you have any).

Sadly, I think the current state of “modern” web development reverses that principle. Developer efficiency is prized above all else. Like I said, that would be absolutely fine if we’re talking about technologies that only developers are exposed to, but as soon as we’re talking about shipping those technologies over the network to end users, it’s negligent to continue to prioritise the developer experience.

Cette formation à l’accessibilité numérique apporte les outils et ressources indispensables pour concevoir et développer des pages web conformément au RGAA. Elle peut s’accompagner d’une certification.

The bottom line is this: we don’t have control over how content is consumed. Users have personal browser settings, the ability to zoom in and out, and various other ways to customize their reading experience. But we do have best CSS best practices we can use to maintain a good user experience alongside those preferences

J’essaye de travailler à rendre le web meilleur et notamment accessible aux personnes handicapées. C’est possible avec mon métier mais on est bien peu de chose face à l’immensité du web.

@media (prefers-color-scheme: dark) {
   filter: invert(90%) hue-rotate(25deg);
   img, video, iframe {
       filter: invert(100%) hue-rotate(-25deg);
   }
}

You know, faster websites mean happier users. It’s absolutely in no doubt. And I just don’t get it, to be honest. I don’t get how people can be working on the web claiming to be doing user centered design and yet, at the same time, ignoring this huge factor.

Good frameworks should provide a better starting point on the essentials (security, accessibility, performance) or have built-in constraints that make it harder to ship something that violates those.

That doesn’t appear to be happening with performance (nor with accessibility, apparently).

Depuis le début du mouvement des gilets jaunes, la gestion du maintien de l'ordre a créé de nombreuses polémiques. Voilà comment le maintien de l'ordre en France a évolué en seulement un an et demi. Avec Rémy Buisine, Charles Villa, Arié Alimi, Nicolas Chapuis et David Dufresne.

Le modèle de justice sociale dominant dans les sociétés démocratiques est généralement présenté comme une combinaison entre égalité des chances et mérite. Ce modèle de justice sociale est fondé sur une double abstraction théorique : l’égalité des chances implique une indétermination théorique de la position sociale par l’origine sociale ; et le mérite implique, de façon complémentaire, une détermination théorique de la position sociale par les contributions ou par les qualités individuelles.

[…] who could define a CSS version? The CSS working group doesn’t seem to feel it has time for it.

Today, we'll look at measuring React component render performance with the React Profiler API, measuring interactions with React's new experimental Interaction Tracing API and measuring custom metrics using the User Timing API.

No class names, no frameworks, just semantic HTML and you're done. Simple, reusable components, for a clean looking design that doesn't get in the way.

Le COVID-19 permet de réaliser plusieurs tests en grandeur nature :

– Test de contrôle de la population (répression, prison, hélicoptères, drones, communications).

– Test d’obéissance de la police dans ce contrôle des populations.

– Test de privatisation-dislocation de l’éducation nationale transférée en e-learning.

– Test d’avancement de la vidéo-médecine à distance.

– Test de soumission des médias, de la population et des gauches (union nationale oblige).

– Test de démolition avancée du droit du travail.

Mais comme toujours, le coût réel de cette surveillance sera supporté par les plus pauvres et les plus fragiles. Les personnes qui ont moins accès aux soins de santé ou qui vivent dans des zones plus exposées aux maladies seront désormais aussi plus fréquemment exclues des lieux et des possibilités ouverts aux autres. […] vous pourriez être considéré à haut risque si vous gagnez moins de 50 000 dollars par an, si vous faites partie d’une famille de plus de six personnes et si vous vivez dans certaines régions du pays, par exemple. Cela crée des possibilités de biais algorithmiques et de discrimination cachée.

It is not uncommon for experts to be told sometimes: "Google does this" or "Apple does that" to justify terrible practices. Except that Apple and Google are just as often wrong as the rest of us. Their notoriety doesn't make them better, it just increases their level of accountability. Nothing more but nothing less.

I'm pretty happy to have cut the size of images on my blog by ~50%. In addition to the benefits to user experience at a critical time, I'm also expecting that this'll save me some money in terms of bandwidth.