News for hackers. Stuff that matters.
Re:Show HN: Beaker – A browser for IPFS and Dat by qwertyuiop924 on Thursday August 11, 2016 @06:15PM (#12272022)
This introduced me to IPFS. I was already aware of Matrix, which had a lot of very cool work done on it, which very much sold it to many of us as "what XMPP should have been." Although XMPP is still a very viable protocol...

OTOH, I've heard a lot of dodgy things about Etherium, particularly from the currency side, and just the security in general.

IPFS is exciting, looking very much like Freenet from a publishing perspective, but without making anybody who want to see that data download a very cumbersome program (and the security, of course). The history system is also interesting. However, the single client and server implementation concerns me. Especially because it's written in Go. I don't make judgements about code quality by language (plenty of good programmers hack in Node and other JS environments), but if we're going to use this thing as the distributed platform of the future, it had better be cross-platform. And Go has a... Less than exellent track record for being easily ported (I won't go so far as to say that Golang Is Trash, but that post alone speaks volumes about the porting experience, and there have been plenty of others). Plenty of organizations run on BSD, Solaris, Illumos, or another Unix. If the future is coming, I'd rather they be part of it, and even if Go runs for them, I'd rather not make it any harder on then than necessary.

Re:Show HN: Beaker – A browser for IPFS and Dat by viraptor on Thursday August 11, 2016 @08:20PM (#12272705)
You realise you're talking about system with 3 live implementations (one complete/reference) https://github.com/ipfs/ipfs#protocol-implementations with the reference implementation being tested on every commit on linux+osx, working on freebsd (https://www.freshports.org/sysutils/ipfs-go/), and windows (https://github.com/ipfs/go-ipfs/blob/master/docs/windows.md), right? Finding other systems left as an exercise to the OP.
Re:Show HN: Beaker – A browser for IPFS and Dat by qwertyuiop924 on Thursday August 11, 2016 @08:48PM (#12272805)
Sorry. I clearly didn't do my research well enough.

But so many of these systems have only one implementation, and no spec. Matrix, Dat, and IPFS are all ahead of the game on that, even though Matrix has only one server implementation, AFAICT, and all the Dat tooling I've found is in node. It's better than Scuttlebot, in any case.

Re:Show HN: Beaker – A browser for IPFS and Dat by wesleytodd on Thursday August 11, 2016 @07:55PM (#12272592)
> And Go has a... Less than exellent track record for being easily ported

I'm not sure what you are talking about with this, but I thought Go had great cross platform support. Can you point me to a resource documenting your "Less than excellent track record"?

Re:Show HN: Beaker – A browser for IPFS and Dat by qwertyuiop924 on Thursday August 11, 2016 @08:29PM (#12272737)
"Golang is Trash" (http://dtrace.org/blogs/wesolows/2014/12/29/golang-is-trash/) is now the classic bashing of Go's implementation, it doesn't talk about issues encountered porting it, which is what I was talking about. The post I referred to in particular was the one by 4ad, who did the solaris port of Go, on this very site (https://news.ycombinator.com/item?id=8817568). However, as I reread it, it becomes clear that the problems it discusses may have been fixed. Nonetheless, Go is a product of Plan 9, and as such, its implementation is... interesting.

The worst horror story is that Go encodes the syscall table on most platforms, which can cause problems on platforms like Solaris, where the syscall table isn't guaranteed to remain the same over time. However, that code's been written, so Go may be better off than I thought.

In general, however, the more implementations, the better. So I maintain that we should build more implementations of the IPFS and dat protocols (they're apparently fairly similar). Because if we're building the next web, it cannot be linked to a single platform, especially if that platform is node, the only platform that all these new protocols seem to have bindings for.

Why? Because a lot of people don't like Node...