Because other sports still don't have (from the article) an almost guaranteed chance of brain damage long-term. That's what we can literally see from differences in the brain tissue, not even considering what we can't see and don't know.
It's singled out because it's the single sport that appears to lead to life-altering effects from invisible injuries, rather than an acceptable cost/risk of accidental injury or increased chance of extremely rare events in other sports. They are open for debate just the same if evidence comes to light.
The real question is why you believe your personal experience has any bearing on the facts presented, to the point of farcical argument. It's a shame that anything we enjoy may later turn out to be harmful, but you are arguing the equivalent of: "I smoked all my life and I'm fine", "but red meat gives you cancer too", "why are you targeting smoking when people drink", "people have died choking on air".
Of course. But we’re talking about children. And children playing is vital to any high level sport. Nobody starts playing anything at the age of 18 and goes on to become a top player.
This is exactly the approach I advocate for, always rerendering whole app on any data update. The components are very simple, basically just views parameterized by passed in props. The data fetch is in one place. Components notify top level on data change which necessitates a fetch/rerender
Unfortunately I get shouted down by those who think we must be maximally efficient even though in makes little difference in render time, and hate “prop drilling”
React is actually more functional than anything else.
Of course if you actually try to be pure functional many developers will scream at you “prop drilling! Code smell!” But to me that it is a much lesser evil than useContext() and what is essentially global variables
An important trait of good functional code is use of persistent data structures. JS code using React is anything but that with state hidden across numerous tiny functional closures.
The only language/framework that is truly functional in that sense is Elm.
I say this as someone who has done their fair share of Haskell, this just isn't a problem in practice, unless you're inexperienced or working with no experienced people.
I get this isn't everyone, and not everyone has the luxury to work in settings where this is a nonissue, but in those settings it sounds like the technology is being used as a restraint jacket for dysfunctional organisation.
When its been a problem, its always because the organisation was dysfunctional, "design" and "engineering" was what people did post humorously to justify spending time on their hobby horse.
Like 99% of components I've written project props on into other components and interpret them in purely. I often manage application state in external stores, which are decoupled from the view.
I should have mentioned language/framework for JS. The thing with Elm is that it gives a straightforward way (even if verbose) to design the whole app around persistent data structures. That gives so many benefits especially long term (time-travelling debugging support, easy insights into app state, full coverage by unit tests etc.). On the other hand my experience with React is that the state hidden in all those functional hooks is hard to debug and reason about with completely unpredictable and non-intuitive behaviour. I think the switch from class components to hooks was a big mistake.
No, banks are something fundamentally different, If you loan someone else your own money, you are just a creditor. What makes banks special is they loan out other peoples money (deposits)
No, it means Trump can continue doing pretty much whatever he wants with little consequence. He certainly didn’t need Republican consent for bombing Iran or his trade wars or for cutting off Ukraine and buddying up to Putin
reply