4 ms·
> Sure your JSON rules might not be ambiguous, but they are not standard either so every competitor aiming for compatibility will have to adhere to these specif
by AnimalMuppet 5y ago
> Sure your JSON rules might not be ambiguous, but they are not standard either so every competitor aiming for compatibility will have to adhere to these specific rules.
Every competitor aiming for compatibility with exactly the set of garbage JSON you will accept, no more and no less will have to adhere to those specific rules. That's... not an especially worthwhile goal for a competitor.
[Edit: Now, if you output something weird, others might have to be compatible. But this was talking about outputting strictly standard JSON.]
- tomtomtom777 5y ago> That's... not an especially worthwhile goal for a competitor. But it is. Because otherwise we're just embracing monopolies. We can't switch to X because it doesn't accept our input as well as the "main" implementation does. You can only beat BIND, or Postfix or Excel if you at least understand what they understand.