But what about hooks? These essentially break this point completely. Functions that literally have (side) 'effect' in the name! (useEffect) Over the past few y

But what about hooks? These essentially break this point completely. Functions that literally have (side) 'effect' in the name! (useEffect) Over the past few years, at least on the frontend, I've found in every case what is a class could be expressed in a function or variety of functions. So yeah, still unsure about this point, maybe it was more for other software domains (backend, embedded, etc) Funny too about what you say about 'grouping functions in some way'... I just made a post about how it makes a lot of sense to put a single function per file... with my organizing, a named folder is the only thing that 'groups' my functions together... so far this style of organization is working well for us. https://chrisfrewin.medium.com/advanced-code-organization-patterns-the-case-for-one-function-per-file-da68c15826e8 https://chrisfrewin.medium.com/advanced-code-organization-pa...