News for hackers. Stuff that matters.
Re:Nike Open Source Software by jessedhillon on Thursday June 30, 2016 @06:05PM (#12012187)
I think parent probably means, why do they write their own instead of using one of the several off-the-shelf solutions available.
Re:Nike Open Source Software by ctvo on Thursday June 30, 2016 @07:17PM (#12012635)
Hey look at these other companies writing their own software too. It's crazy:

A taxi company: https://github.com/uber A hotel company: https://github.com/airbnb A clothing company: https://github.com/gilt

Re:Nike Open Source Software by choward on Thursday June 30, 2016 @07:30PM (#12012702)
We're talking about JSON parsing here: a solved problem. Do those companies write their own JSON parsers? I don't think so.
Re:Nike Open Source Software by ctvo on Thursday June 30, 2016 @07:54PM (#12012838)
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.

Thanks for contributing to open source, Nike!

Re:Nike Open Source Software by girvo on Thursday June 30, 2016 @08:52PM (#12013089)
> 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.

Re:Nike Open Source Software by bearzoo on Thursday June 30, 2016 @08:24PM (#12012988)
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.
Re:Nike Open Source Software by mikestew on Thursday June 30, 2016 @09:45PM (#12013322)
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.)

Re:Nike Open Source Software by stephenr on Friday July 01, 2016 @01:17AM (#12014021)
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.
Re:Nike Open Source Software by mschuster91 on Friday July 01, 2016 @03:12AM (#12014376)
<3
Re:Nike Open Source Software by cmdrfred on Thursday June 30, 2016 @08:47PM (#12013067)
I bet they were on the fence about it and decided let's just do it.
Re:Nike Open Source Software by nemothekid on Friday July 01, 2016 @12:53AM (#12013957)
Even worse - They write their own url encoders:

https://github.com/uber/multidimensional_urlencode

Re:Nike Open Source Software by collyw on Friday July 01, 2016 @10:55AM (#12016510)
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.
Re:Nike Open Source Software by nemothekid on Friday July 01, 2016 @12:51AM (#12013942)
The 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.