4 ms·
At least the original article has some reasoning. You just say "no". This is not very useful. You also assert it's "completely wrong" without any evidence. Read
by lmiller1990 4y ago
At least the original article has some reasoning. You just say "no". This is not very useful. You also assert it's "completely wrong" without any evidence. Reading between the lines, it's more like "I disagree with almost 100% of this post, the author's opinions differ from mine".
> Decoupling logic from components: 100% never do this. Ever.
Care to elaborate? I much prefer to decouple my business logic from my components - mixing logic with the view layer doesn't seem like a great idea, at least ime.
I've also had a good experience with a single folder containing all the relevant code for a component (types, style, test, etc).
- basicallybones 4y agoI'm not the original commenter, but see the 2019 update on this Dan Abramov article: https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0 https://medium.com/@dan_abramov/smart-and-dumb-components-7c...
- lmiller1990 4y agoI'm still not really sold; obviously not good to be overly dogmatic, but MVC taught us the value in putting business (M) in a separate module to the view (V) and hooking them up via a controller (C). Why does all this knowledge suddenly get throw out the window?