[srhtftw]

> So many "best practices" are truly repugnant like ...list of things

I have my own love/hate relationship with many of the things you list and I currently share many of your preferences. However I didn't always see things that way. Best practices start as informal approaches to address the problems of the day. After achieving a modicum of success they'll get enshrined by others as languages, features and cultural artifacts giving rise to new problems.

I find the broad tendency of unthinking "best practicification" more troubling than any particular "best practice".

Take OOP as an example. Stroustrup's early C++ presentations argued OOP meant more than "slow graphics" since people at the time were struggling to build graphical user interfaces for machines without much memory. The idea of melding state and behavior made it easier at the time to build complex user interfaces with imperative languages. But OOP isn't a silver bullet. Many attempts to apply the OOP ideas to other domains met with failure.

Fortunately we now have more powerful machines and better tools available to us.

[tonymet]

More powerful machines maybe, but the apps are less responsive

We must still be mindful of hertz, milliseconds , watts, bytes, airtime , watt-hours, thermals