• 89 Posts
  • 376 Comments
Joined 1 year ago
cake
Cake day: July 17th, 2023

help-circle




  • hydroptic@sopuli.xyzto196@lemmy.blahaj.zoneRule
    link
    fedilink
    arrow-up
    10
    ·
    edit-2
    6 days ago

    Pretty much everything that’s not totally inert produces heat, but the point (they claim!) is that these newfangled doodads don’t generate power using that heat.

    So far we’ve mainly been generating power with more and more ingenious ways of heating up water.



  • hydroptic@sopuli.xyzto196@lemmy.blahaj.zoneOuppy rule
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    7 days ago

    On a semi-related note, I was actually radioactive for a few days once, after I got my thyroid nuked.

    What was cool was that it turned out that regular 'ol camera CCDs (like the one in your cell phone) can detect alpha particles, so I naturally pressed my phone to my neck in a dark room and got this video. Those tiny white “flashes” you see are actually all alpha particles (video in a spoiler block so it doesn’t take up half the screen at least on lemmy-ui):

    video

    I verified it by taking more video with the phone away from my body – no flashes!















  • I dint know many OO languages that don’t have a useless toString on string types.

    Well, that’s just going to be one of those “it is what it is” things in an OO language if your base class has a toString()-equivalent. Sure, it’s probably useless for a string, but if everything’s an object and inherits from some top-level Object class with a toString() method, then you’re going to get a toString() method in strings too. You’re going to get a toString() in everything; in JS even functions have a toString() (the output of which depends on the implementation):

    In a dynamically typed language, if you know that everything can be turned into a string with toString() (or the like), then you can just call that method on any value you have and not have to worry about whether it’ll hurl at runtime because eg. Strings don’t have a toString because it’d technically be useless.


  • Everything that’s an Object is going to either inherit Object.prototype.toString() (mdn) or provide its own implementation. Like I said in another comment, even functions have a toString() because they’re also objects.

    A String is an Object, so it’s going to have a toString() method. It doesn’t inherit Object’s implementation, but provides one that’s sort of a no-op / identity function but not quite.

    So, the thing is that when you say const someString = "test string", you’re not actually creating a new String object instance and assigning it to someString, you’re creating a string (lowercase s!) primitive and assigning it to someString:

    Compare this with creating a new String("bla"):

    In Javascript, primitives don’t actually have any properties or methods, so when you call someString.toString() (or call any other method or access any property on someString), what happens is that someString is coerced into a String instance, and then toString() is called on that. Essentially it’s like going new String(someString).toString().

    Now, what String.prototype.toString() (mdn) does is it returns the underlying string primitive and not the String instance itself:

    Why? Fuckin beats me, I honestly can’t remember what the point of returning the primitive instead of the String instance is because I haven’t been elbow-deep in Javascript in years, but regardless this is what String’s toString() does. Probably has something to do with coercion logic.