2 ms·

> 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 p

• qwertyuiop924 10y ago
  "Golang is Trash" (http://dtrace.org/blogs/wesolows/2014/12/29/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 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...