• 19 Posts
  • 1.71K Comments
Joined 5 years ago
cake
Cake day: May 31st, 2020

help-circle

  • Ephera@lemmy.mltoScience Memes@mander.xyzFictional
    link
    fedilink
    English
    arrow-up
    1
    ·
    16 hours ago

    I’m no expert. I probably know too little about the propagation speed of a wave to understand what you mean there.

    But here is a scenario where something is faster than light in the given medium: https://en.wikipedia.org/wiki/Cherenkov_radiation

    As I understand, neutrons and gravitational waves are also bound by the speed of causality, because they have no mass. And I believe, unlike light, they are unaffected by electromagnetic forces that a material exerts, so they would presumably (always?) travel faster than light in that medium.

    I will also say, that from what little I understand of this video: https://www.pbs.org/video/pbs-space-time-speed-light-not-about-light/
    …it sounds like trying to determine the speed of causality by measuring it, is kind of backwards. You’re at best experimentally confirming what has to be a given under our laws of physics.




  • She did the math (with some assumptions), but basically 0.25 mL of lemon juice will turn 500 mL of alkaline water into neutral water:

    This is in the video at 13:16.

    The reason is that pH is a logarithmic scale. Alkaline water has a pH of about 8, which means it has a tenth of the hydrogen ions compared to neutral water at pH 7.
    Lemon juice has a pH value of 2, which is 1,000,000 times more hydrogen ions than there are in pH 8. So, you just need a little bit of lemon juice to increase the hydrogen ions in alkaline water tenfold, which makes it neutral.











  • I agree in general, that a crash is much better than silently failing, but well, to give you some of the nuance I’ve already mostly figured out:

    • In a script or CLI, you may never need to move beyond just crashing.
    • In a GUI application or app, a crash may be good (so long as unsaved data can be recovered), but you likely need to collect additional information for what the program was doing when the crash happened.
    • In a backend service, a crash can be problematic when it isn’t actually necessary, since it can be abused for Denial-of-Service attacks. Still infinitely better than failing silently, but yeah, you gotta invest into logging, monitoring and alerting, so you don’t need to crash to make it visible.
    • In a library, you generally don’t want to trigger a crash, unless an irrecoverable error happens, because you don’t know where it’ll be used.


  • Currently implementing error handling for a library I’m building and the process is basically to just throw all of the information I can find into there. It makes the error handling code quite verbose, but there’s no easy way for me to know whether the underlying errors expose that information already, so this is actually easier to deal with. 🫠