JSON: Validate, Format and Convert It Anywhere
JSON is stricter than the JavaScript it resembles: the four classic errors, the silent big-ID corruption past 2^53, and the conversion toolbox.
JSON is stricter than the JavaScript it resembles: the four classic errors, the silent big-ID corruption past 2^53, and the conversion toolbox.
Listen becomes silent via a sorting trick, 89 needs 24 steps to mirror, and 196 has defeated billions of computations: wordplay with mechanics.
Case conversion has rulebooks and two real traps: it destroys information one way, and it is language-dependent in ways ASCII rules corrupt.
A character is not one thing: the limits that matter, the emoji that counts four ways, the SMS trap that halves your message, and the workflow.
Dedupe is one click and three decisions: matching options, survivor choice, and the sleeper mode that shows only the duplicates.
Sorting has conventions, not just an algorithm: natural sort, the lowercase sink, accent handling, and the options that decide what you get.
Messy lists clean up in four passes if you run them in the right order: the pipeline, the invisible enemies, and every tool mapped by job.
Counting toward and away from a moment, the three choices that define a finish line, round-number milestones, and the live timer’s hidden assumptions.
Three traps hide in timezone math: staggered DST switches, the two ambiguous twelves, and the date line. All three, made mechanical.
The two counts side by side, day-zero and rollover conventions, why holidays defeat automation, and the weeks trick that makes estimation easy.
Hours and minutes are base-60 pretending to be decimal: the carry rule, the 7.45 trap, a worked week of shifts, and where payroll cents leak.
Every log and API speaks a number near 1.78 billion: why 1970, how to read epochs at a glance, and the two traps that bend dates by millennia.