3 ms·
Try using `run` in the return of a React (or similar) component and you'll never go back ;) There is always a balance here. I'm not saying to never extract a n
by mgreenw 3y ago
Try using `run` in the return of a React (or similar) component and you'll never go back ;)
There is always a balance here. I'm not saying to never extract a named function, and there is certainly good reason to do that, especially if the function is called elsewhere or is quite complex.
But, in many cases, the inline logic is more readable because it's right there, and the function really doesn't need a name.
- gtsop 3y agoI will once more agree with the reasoning on the high level, but: From my experience working in big react+ts codebases devs are nesting components and logic way to much, resulting in unmaintainable messes that neeed hours to refactor. This kind of utility enhances this mental model of nesting stuff instead of extracting. I am not suggesting the run utility will break the world, and maybe there are quite a lot legit usecases. But it is the equivalent (exaggerating a bit here) of giving every untrained person a bazooka. They're lack of proper use will cause caos