NaevaTheRat [she/her]

Despite all my rage I’m still a rat refreshing this page.

I use arch btw.

Credibly accused of being a fascist, liberal, commie, anarchist, child, boomer, pointlessly pedantic, a Russian psychological warfare operative, and db0’s sockpuppet.

Pronouns are she/her.

Vegan for the iron deficiency.

  • 1 Post
  • 37 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2024

help-circle

  • vegantheoryclub has both a home cooking (beware the rules re recipes), and a recipes community. There is also a discord linked with lots of pinned and extremely yummy recipes.

    You are absolutely welcome to have a look, and you will not run into moderation issues unless you promote carnism. For example: wow that looks great, I’m going to have it with lamb" is as welcome as pissing in someone’s face, but asking for recommendations, tips, or suggestions is completely fine.









  • No! good question though, but it misses a detail of their molecular geometry/energy structure.

    They’re both allotropes (different forms) of carbon but the way they are arranged atomically is different. Like soot is basically just random balls of carbon (??? bonds), graphite is rings bonded in a plane (3 bonds, a single layer of which is called graphene), and diamond is a network that extends in 3 dimensions with each atom bonded to 4 carbon atoms.

    When you grind them up you are more making smaller and smaller shards of the base material than changing it’s energetic structure, although at the edges it is changing. If you grind pathologically I suppose you would eventually reduce it all to soot.

    The physical properties of stuff is in part altered by the surface configuration when we get extremely small, but in general we just consider the bulk as even tensie tiny fragments of stuff are thousands (tens, hundreds of depending on geometry) of atoms, of which only a handful have different bonds at the edge.




  • Why do people think Python is ducktyped? The syntax is quite explicit, just because x = 5. is shorthand for x = float(5) doesn’t mean it’s doing weird mutations. The closest would be maybe that something like:

    x = 5
    y = 2.
    z = x * y
    

    works (I think) but that’s not exactly a wacky behaviour. It’s not like it ever does the wrong behaviour of casting a float to an int which can erase meaningful data and cause unpredictable behaviour.

    I mean you can (and often should!) give functions/methods type signatures ffs.