Note di Matteo


#web-dev

Dark/light mode

Discussioni sul web su quanti stati dovrebbero avere i toggle modalità diurna/notturna in app e siti. Cito il riassunto da Web Weekly 199:

How much controversy can there be around dark/light mode toggles? Turns out, a lot. Lea Verou kicked off a whole thing. People have opinions on these little two- or three-state toggles.

So, Lea started the discussion by arguing that website visitors don't care about dark mode toggles (I agree) and that they only reach for them when something's off.

A dark mode toggle is a temporary comfort adjustment. [...] It’s situational, it’s immediate, and it’s usually about the environment you’re in rather than a considered long-term stance on color schemes.

From there, she argues that a dark mode toggle should only have two options: the system preference (shown as dark or light) and the opposite. That's smart. Whenever things are different from the system, you can store the preference that's not the system default. If it matches their general settings, there's nothing to do, and if you go back to the system setting, you clear the preference. This approach seems reasonable to me at first sight.

Bramus disagreed, though.

When building these types of control, I think that one of the main goals here should be to keep things predictable for users.

And well, that's a strong point, too, I'd say. A little sun icon that actually means "system preferences" is a bit tricky to understand if you really care about light and dark modes. I tend to agree here, and it seems like a "Agree to disagree." case, but the whole community had feelings about this. Lea shared more feedback in a follow-up post. And it closed with a banger:

And then it dawned on me: all these persistent dark mode toggles I had seen, literally all of them have been on developer-facing sites!

And I think that's what I came to conclude, too. It's an interesting discussion to have but I really don't think normies care too much about two, three, or no dark/light mode states. Things can always be better and smoother, but for this case I think it's just us nerds who love discussing these things. 😅

#599 /
10 settembre 2026
/
16:17
/ #web-dev


RFC 10008

Il nuovo metodo HTTP QUERY (cioè GET con corpo della richiesta) è ora RFC 10008 (Proposed Standard).

#559 /
13 luglio 2026
/
15:19
/ #http#web-dev


Fontastic Space permette di confrontare font per conoscerne la loro precisa occupazione di spazio.

#528 /
16 giugno 2026
/
17:11
/ #web-dev

Le cit. su questo sito hanno un nuovo stile.

Prima:

Dopo:

#316 /
31 gennaio 2026
/
17:55
/ #dev#web-dev


L'azienda dietro Tailwind CSS è in crisi perché con l'AI nessuno compra più il pacchetto di componenti, che era la principale fonte di ricavi per pagare il team:

But the reality is that 75% of the people on our engineering team lost their jobs here yesterday because of the brutal impact AI has had on our business. And every second I spend trying to do fun free things for the community like this is a second I'm not spending trying to turn the business around and make sure the people who are still here are getting their paychecks every month.

Traffic to our docs is down about 40% from early 2023 despite Tailwind being more popular than ever. The docs are the only way people find out about our commercial products, and without customers we can't afford to maintain the framework. I really want to figure out a way to offer LLM-optimized docs that don't make that situation even worse (again we literally had to lay off 75% of the team yesterday), but I can't prioritize it right now unfortunately, and I'm nervous to offer them without solving that problem first.

[...]

Tailwind is growing faster than it ever has and is bigger than it ever has been, and our revenue is down close to 80%. Right now there's just no correlation between making Tailwind easier to use and making development of the framework more sustainable. I need to fix that before making Tailwind easier to use benefits anyone, because if I can't fix that this project is going to become unmaintained abandonware when there is no one left employed to work on it. I appreciate the sentiment and agree in spirit, it's just more complicated than that in reality right now.

(GitHub)

#272 /
7 gennaio 2026
/
22:53
/ #web-dev#ai

Video.js 10

Nel 2026 uscirà Video.js 10, nuova versione dell'ultrapopolare player video JavaScript. Sarà essenzialmente riprogettato fondendo concetti di Plyr, Media Chrome e Vidstack per renderlo compatibile con lo sviluppo moderno a componenti/React.

#180 /
25 novembre 2025
/
09:54
/ #video#web-dev