And since we're talking about github, haven't they already launched a highly successful pair of projects in atom/electron, in areas where both had competition? why start with negativity before we see what they come out with?
I would accuse them of NIH if they simply reinvented another wheel when there was a perfectly acceptable solution already out there. But it doesn't seem like that was the case. Instead they clearly evaluated the existing solutions, found shortcomings, and decided to solve those problems for themselves, and then publish the resulting code. I see nothing wrong with that approach.
I'm skeptical that Github's load balancing requirements are that different from any of the other large file hosts and SaaS companies. But it's possible and I'm not in a position to tell. That being said, the "NIH syndrome" is a largely overlooked problem in our industry and I think it's reasonable to raise concerns over new projects that may be reinventing the wheel.
wget -c --limit-rate=200K http://support.apple.com/downloads/DL1833/en_US/osxupd10.10.5.dmg
-c resumes download where left off, the rate limiting can be used to match the speed of your connection or intermediaries reducing stalls, drops and angry network users. I would often keep a list of URLs in `download-queue.txt` and use the above flags with -i to load the list of urls, letting it run overnight at some much lower speed.https://gist.github.com/dbr/294151
extracting cookies out of Safari so I could download developer binaries from apple.
It isn't as simple as here's my massive rewrite, click the accept button and everything works out for the open source community.
Let me be the first to say that the level of politics, circle jerking and knowing people is ridiculous.
I have >3 month old pull requests to add tests which have never been looked at - whereas someone who knows the project maintainer will get a PR looked and merged the next day.
True open source fashion is also the freedom to work on whatever you want.
"Just think about it, if they would have contributed to foo instead of working on bar, then foo would be twice as good!" keeps being thrown around every time someone announces something new around here.
Open Source is about just that - allowing anyone and everyone to have access to the source and (if free) making their own version.
There never needs to be justification to write something from scratch, even if it's been done a million times before.
You can appreciate open-source, you can wish that proprietary code was open source, but you never have the right to tell people what they should do, nor are you ever likely to be correct as to what they should do - you are not them.
Many existing open source solutions are optimized for short lived HTTP requests and don't address the long running connection issue (like a large git clone). We wanted something better for our use case.
Sure about the long running connection issue being solved? :-)
I'm bothered by the increasing prevalence of "never invent here".
FOSS is great, but if it's not meeting your needs then writing your own is perfectly valid.
Two reasons.
1) Recruiting. Check out our awesome code! Don't you want to work on this too?
2) Our unique problem today will be the problems of everyone in three years.
This has borne out with the Netflix opes source. At the time it was a problem unique to Netflix -- now a bunch of people are using that software or derivatives.
Joining a pre-existing project is more reasonable when you just can't replicate the basis of the project without learning a lot of new things.
That's the reason why there's a plethora of compile to JS languages, but only a few actual javascript virtual machines.
It is then justified that their creation is needed because "no one else has these kinds of problems" but then they open source them as if lots of other people could benefit from it. Why open source something if it has an expected user base of 1?
Again, I am not surprised by this. They whole push of Github is not to create a community which works together on a single project in a collaborative, consensus based method, but rather lots of people doing their own thing and only occasionally sharing code. It is no wonder that they follow this meme internally.