4 ms·
This is the kind of attitude that makes people, companies, researchers hesitant to publish code online. Its free code for everyone to see, they don't owe you an
by zaptheimpaler 2y ago
This is the kind of attitude that makes people, companies, researchers hesitant to publish code online. Its free code for everyone to see, they don't owe you anything. Its not necessarily a "product" for your consumption, its just a repo.
- esafak 2y agoI don't think so; this is a corporate project, not an enthusiast's. They probably had to internally justify building it over using an existing solution, so they could simply share their rationale. I am not trying to rain on their parade.
- fforflo 2y agoIt's a library written by some devs who thought it might be useful to others, too, and/or are proud enough to share their work. It's not that they'll publish it in an SEC filing. For every n-th solution in the market, n-1 existing ones could have been used, but they weren't for (many times) good reasons. And looking at their Makefile and pyproject.toml I can see that they knew what they wanted.
- klohto 2y agoyes, Nike is a corp where everyone sings kumbaya and the engineers have unlimited time to work on and publish libraries they are proud of, they don’t have to deliver specific values at all.
- blitzar 2y agothe kumbaya and coding is only allowed in the 5 minute lunchbreak at the nike sweatshops
- muspimerol 2y agoI think this is a fair criticism. You chose to share this on hackernews, which invites feedback (including constructive criticism). I don't see the problem ¯\_(ツ)_/¯ Do you expect people to only voice praise for open source projects?
- mb5 2y agoWhy do you think the poster is connected with the repo? I couldn’t see any link.
- muspimerol 2y agoI don't. Regardless who posted it, discussion and constructive criticism is warranted in the comments.
- yunohn 2y ago/s Like it or hate it, it’s how social media works. Everyone posts other people’s things, and then more people get together to rip it to shreds.
- koliber 2y agoIt's a fair set of questions, posed fairly directly, without any sugarcoating. If you read it as a ruthless critique, it stings. If you read it as constructive feedback, it can bring the author a lot of value. If the author can clearly show the value proposition of their library, it will get more adoption, and the community and the author will get value. If the author realizes they coded something that is already a well-solved problem, or a poorly-constructed alternative, the author and Nike could gain by throwing this away and going with a better alternative. Personally, I wasted too many hours of my life creating a solution that did not solve any problems. Had I done some thinking and/or market research ahead of time, it would have saved me ton's of time to work on more worthwhile endeavors. Good feedback is worth its weight in gold, even if it hurts a bit to hear it.
- deleted 2y ago[deleted]