4 ms·
Because they also make apps that integrate with the fitness trackers housed in some of their shoes.
by davidlumley 10y ago
Because they also make apps that integrate with the fitness trackers housed in some of their shoes.
- jessedhillon 10y agoI think parent probably means, why do they write their own instead of using one of the several off-the-shelf solutions available.
- ctvo 10y agoHey look at these other companies writing their own software too. It's crazy: A taxi company: https://github.com/uber https://github.com/uber A hotel company: https://github.com/airbnb https://github.com/airbnb A clothing company: https://github.com/gilt https://github.com/gilt
- choward 10y agoWe're talking about JSON parsing here: a solved problem. Do those companies write their own JSON parsers? I don't think so.
- deleted 10y ago[deleted]
- ctvo 10y agoI'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. Thanks for contributing to open source, Nike!
- girvo 10y ago> The level of arrogance to think we know better 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.
- bearzoo 10y agoA "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.
- cmdrfred 10y agoI bet they were on the fence about it and decided let's just do it.
- mikestew 10y agoWe'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.)
- stephenr 10y agoWelcome 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.
- mschuster91 10y ago<3
- nemothekid 10y agoEven worse - They write their own url encoders: https://github.com/uber/multidimensional_urlencode https://github.com/uber/multidimensional_urlencode
- collyw 10y agoYes 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.
- nemothekid 10y agoThe first commit was in July 2015, 9 months after Swift was initially released. It's very possible that an "off the shelf" solution didn't exist yet.
- ajmurmann 10y agoThere also is a SNKRS app that allows you to buy limited edition shoes. Must have for every sneaker head!