4 ms·

Regardless, most dependencies are on GitHub which breaks bower install for most people. It's crazy how much infrastructure relies on this single point of failur

by firloop 11y ago

Regardless, most dependencies are on GitHub which breaks bower install for most people. It's crazy how much infrastructure relies on this single point of failure.

brudgers 11y ago
Someone should make a distributed version control system.
- tedmiston 11y ago
  Or a local cache of dependencies
- adamsea 11y ago
  What would that look like? Can you describe it? It's not very useful to say stuff without providing some sort of useful idea. You can't just say "someone should write some sort of stupid content tracker, and give it some random three-letter combination that is pronounceable," or whatever.
  - such_a_casual 11y ago
    Completely agree. But whoever makes it, they should make it free and open source and designed to handle everything from small to very large projects with speed and efficiency. Additionally, it should be easy to learn and have a tiny footprint with lightning fast performance. It should outclass SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.
    - rodgerd 11y ago
      > it should be easy to learn That would be a significant upgrade.
  - jethro_tell 11y ago
    Can't tell if your serious or not but I suppose that would be properly implemented git.
    - ChickeNES 11y ago
      It's sarcasm: $ man git "git - the stupid content tracker"
- franciscop 11y ago
  Would this be useful? # pre-push (there is not post-push) # Update in several places git push bitbucket master git push gitlab master # ...
- ianopolous 11y ago
  You mean like IPFS? [1] People are working on it. [1] https://ipfs.io https://ipfs.io
  - kelseydh 11y ago
    Their source code pointing to Github is symbolic of exactly how this problem hasn't been solved yet.
    - ianopolous 11y ago
      I didn't say it was solved, but they are very close. IPFS is essentially a global p2p git repo, with a cryptographically controlled branch namespace.
      - kelseydh 11y ago
        That sounds very cool. I was just pointing out how divorced these ideas still are from the way we actually program and implement things on the web. In an ideal world, a link to a source code repository (or a link to anything for that matter...) would never fail because there would be automatic mirrors to at least provide read-only access to it. It sort of forces one to ask whether this is the result of fundamental mistakes within HTTP / DNS itself. It's not realistic for a web designer to put time into making external links fault tolerant by running some query to switch the routing link to an available node.
        ianopolous 11y ago
        Content addressed links at least make this possible. With http you have to reach a particular server. If that server is down, the link is broken. With ipfs all you need is at least one machine on the entire network to be serving a file and the link will work and as an added bonus you can verify the hash of what you get so a mitm attack on that link is impossible.
        kelseydh 11y ago
- brudgers 11y ago
  What a useless comment.
johnhenry 11y ago
Aren't npm installs actually hosted on npm? This shouldn't affect npm installs.
- firloop 11y ago
  Oh wow, color me surprised. I edited my comment.
- clessg 11y ago
  That's right. Except I of course got unlucky. npm i semantic-ui npm ERR! fetch failed https://github.com/derekslife/wrench-js/tarball/156eaceed68ed31ffe2a3ecfbcb2be6ed1417fb2 npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 503
  - johnhenry 11y ago
    So, in this case, it looks like github isn't acting as a version control server, but rather a static server... It turns out that github isn't just a single point of failure for some application, but rather multiple points of failure for slightly different reasons...
- sbruchmann 11y ago
  It is possible to install npm packages that are hosted on GitHub: http://stackoverflow.com/a/17509764/889864 http://stackoverflow.com/a/17509764/889864

by firloop 11y ago

Regardless, most dependencies are on GitHub which breaks bower install for most people. It's crazy how much infrastructure relies on this single point of failure.

brudgers 11y ago

Someone should make a distributed version control system.

tedmiston 11y ago
Or a local cache of dependencies
adamsea 11y ago
What would that look like? Can you describe it? It's not very useful to say stuff without providing some sort of useful idea. You can't just say "someone should write some sort of stupid content tracker, and give it some random three-letter combination that is pronounceable," or whatever.
- such_a_casual 11y ago
  Completely agree. But whoever makes it, they should make it free and open source and designed to handle everything from small to very large projects with speed and efficiency. Additionally, it should be easy to learn and have a tiny footprint with lightning fast performance. It should outclass SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.
  - rodgerd 11y ago
    > it should be easy to learn That would be a significant upgrade.
- jethro_tell 11y ago
  Can't tell if your serious or not but I suppose that would be properly implemented git.
  - ChickeNES 11y ago
    It's sarcasm: $ man git "git - the stupid content tracker"
franciscop 11y ago
Would this be useful? # pre-push (there is not post-push) # Update in several places git push bitbucket master git push gitlab master # ...
ianopolous 11y ago
You mean like IPFS? [1] People are working on it. [1] https://ipfs.io https://ipfs.io
- kelseydh 11y ago
  Their source code pointing to Github is symbolic of exactly how this problem hasn't been solved yet.
  - ianopolous 11y ago
    I didn't say it was solved, but they are very close. IPFS is essentially a global p2p git repo, with a cryptographically controlled branch namespace.
    - kelseydh 11y ago
      That sounds very cool. I was just pointing out how divorced these ideas still are from the way we actually program and implement things on the web. In an ideal world, a link to a source code repository (or a link to anything for that matter...) would never fail because there would be automatic mirrors to at least provide read-only access to it. It sort of forces one to ask whether this is the result of fundamental mistakes within HTTP / DNS itself. It's not realistic for a web designer to put time into making external links fault tolerant by running some query to switch the routing link to an available node.
      - ianopolous 11y ago
        Content addressed links at least make this possible. With http you have to reach a particular server. If that server is down, the link is broken. With ipfs all you need is at least one machine on the entire network to be serving a file and the link will work and as an added bonus you can verify the hash of what you get so a mitm attack on that link is impossible.
        kelseydh 11y ago
brudgers 11y ago
What a useless comment.

johnhenry 11y ago

Aren't npm installs actually hosted on npm? This shouldn't affect npm installs.

firloop 11y ago
Oh wow, color me surprised. I edited my comment.
clessg 11y ago
That's right. Except I of course got unlucky. npm i semantic-ui npm ERR! fetch failed https://github.com/derekslife/wrench-js/tarball/156eaceed68ed31ffe2a3ecfbcb2be6ed1417fb2 npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 503
- johnhenry 11y ago
  So, in this case, it looks like github isn't acting as a version control server, but rather a static server... It turns out that github isn't just a single point of failure for some application, but rather multiple points of failure for slightly different reasons...
sbruchmann 11y ago
It is possible to install npm packages that are hosted on GitHub: http://stackoverflow.com/a/17509764/889864 http://stackoverflow.com/a/17509764/889864