• 0 Posts
  • 75 Comments
Joined 11 months ago
cake
Cake day: August 4th, 2023

help-circle





  • 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

    1. It is difficult to understand: the developer has to open two, three or more different classes to view the whole algorithm
    2. It is inefficient: because the algorithm is distributed over many classes and instances, as the algorithm runs, there are a lot of unnecessary calls (eg one method on one instance has to iterate over many instances of its children, and each child has to iterate over its children) and data has to pass through these function calls.

    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.








  • modeler@lemmy.worldtoScience Memes@mander.xyzCalculus made easy
    link
    fedilink
    English
    arrow-up
    17
    ·
    edit-2
    2 months ago

    I must not use jargon.

    Jargon is the mind-killer.

    Jargon is the little-death that brings total confusion. I will face the jargon. I will permit it to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the jargon has gone there will be clarity. Only sense will remain.



  • Sorry for taking a long time to reply.

    with plain old binary fission cell division, how do you get both to divide at the same time, and give each cell one of the new organelles?

    An excellent question! Luckily it was answered in the paper. The researchers actually had a high resolution soft x-ray movie of cell division (ok, an exaggeration, they had a few micrographs showing the sequence). In the sequence, it showed how the organelles (including the novel N2 fixation one) undergoing division and each ‘child’ organelle ending up in different halves.

    Cell division is controlled in the cell by an amazing process:

    • 2 centres are created on opposite sides of the cell
    • Structures like tethers are built that connect each centre to each of the organelles (the nucleus, mitochondria and the N2 fixators). These are called microtubules
    • The microtubules then start shortening, pulling the organelles in two directions, separating them.

    The x-ray micrographs show that the N2 fixators are already integrated into this mitosis mechanism - my guess is that the N2 fixators already ‘understand’ the parent cell’s mitosis signaling.

    The authors also say that the organelles have lost a number of genes for essential cellular functions, relying on the parent cell to provide those capabilities. By comparison, mitochondria have only 37 genes left, and chloroplasts weren’t known for having any DNA when I was at school, but are now known to have about 110 genes.

    In other words, a lot of evolution has already occurred and they are well on the way to being ‘proper’ organelles.




  • “DI frameworks” are Satan’s farts. Classpath-scanning nonsense that turns compile-time errors into runtime errors. Not only is your Ctr still coupled to your Svc, but both are now coupled to Spring.

    Let’s qualify this: DI frameworks that use configuration files to specify the dependencies are Satan’s farts. You can use the DI pattern but do the injection in source code to get full compile-time type checking and all the benefits of a fully packaged JAR or similar binary. The root of the evil is having text files as part of the packaging, and not having the tooling to treat those files as part of the source code at build time.


  • This is a brilliant idea - not just because it solves the problem of too many homeopaths but because of the way homeopathy ‘works’.

    Homeopathy is the idea that “like treats like” (the homeo is latin for “the same”). So typically the homeopath looks at the symptoms of the disease, finds some poison that causes the same symptoms, then dilutes the hell out of it.

    In this case, what are the symptoms that homeopathy causes? Dumbness. So the ground up homeopath pills would be ideal for treating homeopath users and practitioners. And the Gwyneth Paltrow crowd. So many birds with one stone!