AggressivelyPassive

  • 8 Posts
  • 510 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle


  • That’s decades of legacy for you…

    I bet each step/arrow/decision had a good reason at some point, but most of them probably back when computers lived in caves and hunted their tapes using spears and rocks.

    I feel like we’re slowly reaching a point where the complexity is collapsing in on itself - just look at the absolute chaos a modern web app is.






  • Again, did you actually read the comments?

    Is SQL an API contract using JSON? I hardly think so.

    Java does not distinguish between null and non-existence within an API contract. Neither does Python. JS is the weird one here for having two different identifiers.

    Why are you so hellbent on proving something universal that doesn’t apply for the case specified above? Seriously, you’re the “well, ackshually” meme in person. You are unable or unwilling to distinguish between abstract and concrete. And that makes you pretty bad engineers.







  • That’s exactly not the thing, because nobody broke the contract, they simply interpret it differently in details.

    Having a null reference is perfectly valid json, as long as it’s not explicitly prohibited. Null just says “nothing in here” and that’s exactly what an omission also communicates.

    The difference is just whether you treat implicit and explicit non-existence differently. And neither interpretation is wrong per contract.