• 167 Posts
  • 1.5K Comments
Joined 1 year ago
cake
Cake day: July 17th, 2023

help-circle




  • hydroptic@sopuli.xyzto196@lemmy.blahaj.zoneRule
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    2 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
    3 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!













  • Far as Swift’s syntax goes, I really like argument labels too, but it’s just that there’s SO. MUCH. SYNTAX. Lots of sugar, yes, but sometimes that’s part of the problem in my opinion, because it often adds to the syntactic and semantic “noise.” Also, there’s 98 keywords (more if you count eg. try, try! and try? as different keywords, and this count is missing eg. sending and other new keywords) – compare this to say Rust’s or or Python’s 35. Java’s got 68, while C++ also has 98 and it’s notorious for having way too many of them. And then there’s all the symbols – some of which have different meanings in different contexts.

    It’s true that ARC only applies to reference types, but even with value types you can often get some fairly surprising performance problems due to implicit copies, for example in getters and setters – and the _read and _modify accessors that can sometimes help with that due to returning (well, yielding) a borrowed value instead of a copy aren’t meant for “public” use (which doesn’t mean many libraries etc. don’t use them, much to the consternation of core devs).



  • hydroptic@sopuli.xyzOPtoPolitical Memes@lemmy.worldDear America
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    9 days ago

    Would have cost you exactly 0 € to not be a cunt, but here you are.

    I didn’t correct it because I was away from my computer for an extended period – the current version has a different image and is correctly attributed. I didn’t delete it because then the existing conversation in the comments would have also gotten nuked, exactly the same reason the mod didn’t delete it either.