GA Nostr. I had a laugh about JavaScript’s built-in Date shenanigans, which at this point should mostly be a historical curiosity. Temporal isn’t widely available yet, but JavaScript has a gazillion libraries like date-fns, Luxon, and even the old school Moment.js. Then I remembered that a lot of "modern" codebases will be: - Written by LLMs trained on outdated code - Vibecoded by people who don’t know that the Date API is broken, or even that date & time is a hard problem to solve - Built with little to no incentive to double-check what the code is doing, produce testable requirements, or gain enough context to at least know they should instruct "agents" to write better code and skip JavaScript’s Date API - Used by people who mostly won’t even notice when a parsing bug results in some dates being in 1970, others in the 2000s, some in the future, etc, etc, etc And all of these apps will produce data. Data that will be published, stored, and consumed by other applications built in the same fashion, treating it as "facts". "Facts" that business applications will rely on to make important decisions, often handled by people who are nowhere near sufficiently trained or incentivised to double-check or even care about this. It’s... scary. #gm #JavaScript #funnyUntilItsNot