• 1 Post
  • 254 Comments
Joined 2 years ago
cake
Cake day: September 24th, 2023

help-circle
  • Try interacting with anything that uses u64 and you’ll be a lot less happy!

    Anyway JavaScript does have BigInt so technically you are choosing.

    that insanity is how C and Intel handle NaN conversions.

    It’s not actually quite as bad as the article says. While it’s UB for C, and it can return garbage. The actual x86 conversion instruction will never return garbage. Unfortunately the value it returns is 0x8000… whereas JS apparently wants 0. And it sets a floating point exception flag, so you still need extra instructions to handle it. Probably not many though.

    Also in practice on a modern JS engine it won’t actually need to do this operation very often anyway.


















  • Even if there are tight time constraints, you won’t sacrifice quality, because that would make you slower.

    Too right. People find this so hard to understand. I think they dramatically underestimate the payback time on technical debt.

    I am currently working in a startup that has the classic “we’re a startup, quality doesn’t matter” attitude. They think that they might not be around in a year so it’s best to go fast and not give a shit about tech debt.

    In my experience that attitude bites in under 6 months. I’m already wasting entire days sorting out messes that they neglected to deal with.


  • I mean, it would be great if this succeeded… ffmpeg is nice and all but its interface is clearly terrible and there’s absolutely no way it is remotely secure. Anyone that uses it on a server basically has to run it in its own VM, or a severely locked down sandbox.

    But good luck supporting all the codecs people expect. I’m not even talking the obscure ones ffmpeg supports; just the ones “normal” people use will be a life’s work.

    Also you have to change the name!