If the best practice is not the default and needs to be remembered and applied explicitly, it‘s just horseshit design.

Take that React devs!

I feel like this is a lost-in-translation problem. Say a new version of something comes out - a library, a framework, whatever - and the devleoper/team shows you the default use. Then another someone comes around and shows their specific use case which might be different than the default - and a bunch of people start parroting that without fully understanding it, for some reason only remembering that it's better than the default.

@whimsical How can I give multiple ++ (look at useEffect ;P)

they call it a "practice" for a reason. Because you have to remember to do it.

Although, from my experience, "practice" is a synonym for "an oversight".

Library and language warts are the mother of "best practice".

Thats how we got javascript after all.