[HN Gopher] Iroh: A New Implementation of IPFS
       ___________________________________________________________________
        
       Iroh: A New Implementation of IPFS
        
       Author : dannyobrien
       Score  : 56 points
       Date   : 2022-10-28 19:15 UTC (3 hours ago)
        
 (HTM) web link (iroh.computer)
 (TXT) w3m dump (iroh.computer)
        
       | faitswulff wrote:
       | This library paves the way for Zuko, an impetuous young
       | interplanetary computation system.
        
         | pcthrowaway wrote:
         | Zuko will boast 50% more honour than Iroh.
        
         | lcnPylGDnU4H9OF wrote:
         | In case someone is confused by this comment:
         | https://en.wikipedia.org/wiki/Avatar:_The_Last_Airbender
         | 
         | (The character Iroh is the uncle of the character Zuko.)
        
         | superkuh wrote:
         | Gotta wait till someone figures out how to implement proof of
         | honor.
        
           | evilos wrote:
           | Powered by hot leaf juice.
        
       | mdaniel wrote:
       | > We are targeting the end of October 2022 for an initial
       | version,
       | 
       | heh, they better hurry :-D
       | 
       | but seriously, I hope this cures some of the oft-reported perf
       | woes with go-ipfs
        
         | jandrese wrote:
         | Yes. I experimented with the go IPFS client but stopped using
         | it after noticing that even a fairly small share was burning up
         | 75% of a CPU core all of the time.
        
           | Thaxll wrote:
           | Not sure how the Go implementation is but by design IPFS is a
           | very slow protocol.
        
           | diegocg wrote:
           | How is Rust or any other language supposed to help with this?
           | Unless there is a serious design problem in the current go
           | codebase, removing GC overhead will not by itself solve the
           | problem of some software having to run all the time
        
             | lijogdfljk wrote:
             | Yea... i'm a huge fan of Rust and it is my primary language
             | these days, but despite my many complaints with Go.. it's
             | not bad. In fact it's pretty solid. I can't imagine the
             | primary slowness in ipfs-go will be solved by ipfs-rust, at
             | least on language alone. Some, sure, but not primary.. i
             | would think.
             | 
             | Do i think Rust _could_ have a better, more generic library
             | with code that is far more concise than Go? Yes.. but that
             | 's not likely the cause for ipfs-go's issues.
             | 
             | I can definitely see a chance for a rewrite producing
             | better code though. As much as i'd love to give Rust that
             | victory, i just can't imagine Rust is _that_ big of
             | contributor in this specific case.
        
             | wongarsu wrote:
             | I'm not sure people are claiming that the choice of
             | programming language is the deciding factor? All the
             | website and the comments are saying is "the current client
             | (which happens to be written in go) is slow, maybe this
             | rewrite will be faster". I'm not sure it's fair to read it
             | as an attack on go, or an endorsement of rust.
        
       | nocobot wrote:
       | looking forward to playing with this!
       | 
       | FYI: the github link (when clicking from the docs, not the
       | landing page) is broken
        
       | vfclists wrote:
        
         | ummonk wrote:
         | I normally disagree with people criticizing websites for
         | focusing on style instead of having an ugly 2000s interface,
         | but I have to agree with you on this. This website is extremely
         | difficult to navigate.
        
         | tptacek wrote:
         | _Please don 't complain about tangential annoyances--things
         | like article or website formats, name collisions, or back-
         | button breakage. They're too common to be interesting._
         | 
         | https://news.ycombinator.com/newsguidelines.html
        
         | mattlondon wrote:
         | The use of the "fi" ligature on a fixed-width font is also
         | extremely jarring.
        
       ___________________________________________________________________
       (page generated 2022-10-28 23:01 UTC)