nhoizey

nhoizey, 4 days ago to random French

🤮

nhoizey, 4 days ago to random French

#AVote 🗳️

Pour la première fois avec ma grande, fier !

nhoizey, 4 days ago to random French

Je sens que je vais me régaler !

(Dommage que les noms des auteurs soient si peu lisibles, étrange choix typo.)

nhoizey, 6 days ago to random French

“An even faster Microsoft Edge” by Microsoft Edge Team

🔗 https://blogs.windows.com/msedgedev/2024/05/28/an-even-faster-microsoft-edge/

> JavaScript must be downloaded, then run through a JIT compiler (even if you don’t use it), and then executed, and all this must be done before any of the JavaScript can start rendering the UI. This introduces a lot of delay before users can see the UI, especially on low-end devices.

#WebPerf

⚓️ https://nicolas-hoizey.com/links/2024/05/29/an-even-faster-microsoft-edge/

nhoizey, 6 days ago to random French

“Why Lighthouse Performance Score Doesn’t Work” by @fox

🔗 https://calibreapp.com/blog/downsides-of-performance-score

> There is some correlation between the [Lighthouse] Performance Score and how well your site will do for real users. Still, lab testing alone doesn’t capture all speed issues (similarly, field testing might prove inadequate in showcasing other speed problems). That’s why relying on Performance Score is not a bulletproof strategy. We…

#WebPerf #Lighthouse

⚓️ https://nicolas-hoizey.com/links/2024/06/07/why-lighthouse-performance-score-doesn-t-work/

nhoizey, 6 days ago to random French

““Web components” considered harmful” by @mayank

🔗 https://www.mayank.co/blog/web-components-considered-harmful

> This is a branding problem as much as it is an education problem. Neither the HTML standard nor the DOM standard mentions the term “web components” anywhere. And yet it’s present everywhere in documentation and learning material.

#WebComponents

⚓️ https://nicolas-hoizey.com/links/2024/05/29/web-components-considered-harmful/