3 ms·
You could have said the same thing about Java in 1996. Saying there's a lot of hype around Go isn't particularly interesting. Claiming that Go isn't suitable
by loudmax 13y ago
You could have said the same thing about Java in 1996. Saying there's a lot of hype around Go isn't particularly interesting. Claiming that Go isn't suitable for some particular purpose, or even any particular purpose is more interesting as long as you explain your reasoning. The author if this post explains why he switched to Go, and that is interesting and informative.
Maybe three years from now, Rust will be ready for production use and switching from Go to Rust will help people become more productive and we'll see blog posts about it. This is how progress works and it's nothing to scoff at.
- wpietri 13y agoSaying there's a lot of hype around something is very interesting to me. The hype cycle has well-known biases. Knowing when a product is peaking is helpful to me, in that I can basically ignore 95% of the noise about it. This post is a fine example. He could have written exactly the same post about C, because he's basically saying "compiled binaries are easier to distribute". He's been blogging about Go for an entire two weeks. The only potentially new information here is "Go produces a binary." That's not to say he shouldn't have written the post. He learned something and he shared it, which is great. It's just that nobody would be talking about the C version of the post, because that's not the hyped technology.
- muaddirac 13y agoI got more something like: "I love writing a cli in a nice, expressive language like ruby, but ruby is a pain to distribute. I wrote this library for Go that lets me write simply and expressively, and I still get the advantages of Go's portability." Not a groundbreaking revelation, but his point, I thought, was the expressiveness of the syntax PLUS the portability of the code.