Archives

• Nicolas Hoizey
• 21 December 2022
• Google, Lighthouse, WebPerf
• 15 reactions
• permalink

Same page tested on PageSpeed Insights over a few hours the same day, without anything modified, and the desktop scores vary from 19 to 59… 🤷‍♂️

A lot of businesses rely on this crap to now if their site is "fast" enough for Google SEO! 😭

• Nicolas Hoizey
• 18 December 2022
• esviji, game, responsive, SVG
• 2 reactions
• permalink

I wonder why there are not so many Web games using mostly HTML, CSS and #SVG for the UI, with all the #responsive power they have… 🤷‍♂️

This live demo is more than 6 years old: https://play.esviji.com/wow/

(Remove wow at the end to really play… 😅)

• Nicolas Hoizey
• 18 December 2022
• Twitter
• permalink

going forward, Twitter will no longer allow free promotion of specific social media platforms on Twitter
— Twitter's promotion of alternative social platforms policy

Emon Lusk is so afraid. 🥳

• Nicolas Hoizey
• 16 December 2022
• CSS, Flexbox, JavaScript
• 3 reactions
• permalink

While we wait for browsers to implement the text-wrap: balance; #CSS property and value for text (pleeeeeease! 🙏), I may have created a silly — and probably sub-optimal — function to do it with HTML block elements:

https://codepen.io/nhoizey/pen/mdjbrVx

Tell me what you think!

But why? Just because a colleague needed it, we could not find a solution in pure CSS, and I like challenges… 😅

• Nicolas Hoizey
• 14 December 2022
• WebPerf
• 3 reactions
• permalink

In all #WebPerf reporting tools with graphs, I would like to be able to quickly set a preferred scale, or ignore certain values that I know are incorrect.

Examples from Contentsquare/Dareboost and SpeedCurve…

• Nicolas Hoizey
• 14 December 2022
• JavaScript
• 8 reactions
• permalink

I needed a JavaScript way to verify if two arrays contain the same (all different) values.

I then found a better solution for my use case, but it might be useful later, so here it is:

const sameValues = (array1, array2) =>
  array1.length === array2.length &&
  array1.every((element) => array2.includes(element));

• Nicolas Hoizey
• 14 December 2022
• Mastodon, UX
• 8 reactions
• permalink

It's pretty annoying to see the same toot repeatedly on #Mastodon because everyone is boosting it, even if it's legitimately awesome.

Currently, a boost of a toot is only posted if at least 40 other toots have been posted since the previous boost of the same toot.

There is a GitHub issue asking to allow the user to change this number, or set a duration instead:
https://github.com/mastodon/mastodon/issues/18693

Please vote!