![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/913b482d-9012-449f-bc87-b1f4463e7154.jpeg)
The reference if you haven’t seen it.
Dara Ó Briain is a legend!
The reference if you haven’t seen it.
Dara Ó Briain is a legend!
That was one of the original proposed mechanisms to explain how the (obviously false) autism was caused.
But since then, since thiomersal was removed, other ‘causes’ and moral issues have been invented, including cells from abortions.
The one that makes me laugh the most is that it’s terrible that the poor poor baby is exposed to so many illnesses (measles, mumps, rubella, polio, tetanus, notovirus, rotovirus and more) in such a short space of time, it’s no wonder the poor dear’s immune system is compromised. And then the same mother drops the kid off at daycare and exposes the poor dear to all those viruses and more - and live viruses at that.
There is no bleeding logic, just feels. And they get so angry at the fake harm that medicine is causing, and simultaneously actually causing real harms to real people.
I don’t think that the anti-oop collective is attacking polymorphism or overloading - both are important in functional programming. And let’s add encapsulation and implementation hiding to this list.
The argument is that OOP makes the wrong abstractions. Inheritance (as OOP models it) is quite rare on business entities. The other major example cited is that an algorithm written in the OOP style ends up distributing its code across the different classes, and therefore
Instead of this, the functional programmer says, you should write the algorithm as a function (or several functions) in one place, so it’s the function that walks the object structure. The navigation is done using tools like apply
or map
rather than a loop in a method on the parent instance.
A key insight in this approach is that the way an algorithm walks the data structure is the responsibility of the algorithm rather than a responsibility that is shared across many classes and subclasses.
In general, I think this is a valid point - when you are writing algorithms over the whole dataset. OOP does have some counterpoints encapsulating behaviour on just that object for example validating the object’s private members, or data processing for that object and its immediate children or peers.
stop using it
Are the MAGA crowd actively cancelling products now?
What about the people who lived in the Americas or the Pacific 1800 years ago? These people could not have heard of Jesus as missionaries could not have spread any word to them at this time.
(And while I’m about it, Christianity was a whole different thing back then - the Trinity hadn’t been invented, there were multiple sects with very different ideas, what books would be in the New Testament had not been decided, etc etc. People with beliefs of that time would seem highly unorthodox today, and the Christianity of today would be seen as heretical by those in the 3rd century, so who’s going to heaven again?)
Purgatory was invented for the purpose of not sending good people who had not heard of Jesus to hell. But still, these people were denied their chance to get to heaven which seems mighty unfair.