I'm sure they had no idea it was a solved problem in Swift and are very embarrassed...
The level of arrogance to think we know better than the developers working at a company on what they should / shouldn't write is astounding.
Nike doesn't need to justify anything to any of us, though as someone who writes apps using Swift, it looks distinctly different from other JSON parsers. I'll explore using it in a future project.
Somewhat prevalent here on HN, I've noticed. Middlebrow dismissals and condescending comments that fail to consider context seem to be even more regular than normal lately, though that's probably just my mind playing tricks on me.
A "solved" problem? I think that is a ridiculous thing to say. Just because people know how to parse json does not mean there aren't solutions that are more performant or useable. Shit maybe they just wanted to parse and collect frequency counts of keys or something all in the same pass? There are reasons to do so.
We're talking about JSON parsing here: a solved problem.
Solved for your use case(s), you mean. You're saying that you cannot imagine a reasonable circumstance under which off-the-shelf solutions wouldn't fit your needs? (Hint: if you write code for a living, this very scenario is why you have a job.)
Welcome to Developers 2.0, where writing a program means duct-taping together 500+ 'micro libraries' (each of which has a dependency tree like fucking crab grass) with maybe a dozen lines of bootstrap code.
Yes it amuses / frustrates me that people site working with JSON as a reason for using node.js. Every mainstream language can parse and create JSON trivially.
A taxi company: https://github.com/uber A hotel company: https://github.com/airbnb A clothing company: https://github.com/gilt