5 ms·

I must have hit a nerve. > The reason go is a good investment because it has alot of good investors investing in it. A lot of good investors invested in Mongo

by codexon 14y ago

I must have hit a nerve. > The reason go is a good investment because it has alot of good investors investing in it. A lot of good investors invested in MongoDB. > Time yes, Money no. Developers may charge money to produce software, however there are lots of software projects out there that were written by developers who worked for free. Have you ever been in a startup before? Spending months reinventing the wheel while competitors are working on business logic is a great way to set yourself permanently behind. > As if its likely to fail? Go has already successfully satisfied the language designer's desires that motivated the project's creation. Besides Vitess, what other high profile usage is there at Google? Not to mention they offloaded part of the implementation to Memcache because Go wasn't good enough. > Are you kidding me? Google has some of the most well respected engineers in computational history working full time on Go. You don't need Turing award winners to flesh out solid libraries. Go doesn't even have a precise GC and still won't have one by 1.1.

pjmlp 14y ago
> I must have hit a nerve. No, you just got hit with the typical Go activism reply when someone mentions issues with the language.
- _ak 14y ago
  Issues? What issues? Most complaints about Go are really just "it doesn't contain my favorite language feature", "I heard the GC isn't even precise so it must suck", "it's too immature", "I couldn't get this library to work within 10 minutes so Go sucks", etc. pp., but people are simply unable to point to any actual pain points that hinder productive use of Go.
  - ithkuil 14y ago
    I really love go, I try to use it whenever I can. That being said, I still have the feeling that having to rewrite a lot of dummy boilerplate code because of lack of generic collections hinders my productivity. I completely understand that introducing that in the language it's a pandora box, etc etc (not only because of compiler's complexity and compilation speed). But still, I have to find a way around that, being DRY has obvious advantages (although depending too much on obscure magic can be a problem); it's not just a random language feature from my favorite language. I'm trying to see whether https://github.com/droundy/gotgo https://github.com/droundy/gotgo helps
    - _ak 14y ago
      > I still have the feeling that having to rewrite a lot of dummy boilerplate code because of lack of generic collections hinders my productivity. Can you give any concrete code examples including a description what you would have liked differently?
  - codexon 14y ago
    With your logic, the same argument could be applied to PHP. The problem is that Go simply doesn't solve anything new. If Go contains your favorite language features but not mine, then why should I bother to use or hype it? If you want lightweight concurrency with GC you could have gone with Scala, Erlang, or Haskell.
_ak 14y ago
> Besides Vitess, what other high profile usage is there at Google? The piece of software that runs on dl.google.com, which serves millions of Chrome updates every day, is written in Go. The problem is: you're asking for Go success stories at Google, even though most of Google's internals will never be published. Why don't you just take a closer look at other companies' success stories and acknowledge them? > Not to mention they offloaded part of the implementation to Memcache because Go wasn't good enough. Huh, what? Using memcached means the technology you use isn't good enough, or what are you trying to suggest? Don't forget that the author of memcached is a core Go developer at Google, so I'd say they know what they're doing.
- bobbydavid 14y ago
  Can anyone explain why this was downvoted?
  - _ak 14y ago
    Because HN jumped the shark and is now basically Reddit in a different color theme.
  - codexon 14y ago
    I didn't downvote it, but it was downvoted for a good reason. He didn't spend much effort to understand a simple sentence. http://code.google.com/p/vitess/wiki/ProjectGoals#Why_did_we_choose_go http://code.google.com/p/vitess/wiki/ProjectGoals#Why_did_we... > Go’s existing mark-and-sweep garbage collector is sub-optimal for systems that use large amounts of static memory (like caches). In the case of vtocc, this would be the row cache. To alleviate this, we intend to use memcache for the time being. For a self-described systems level language this is ridiculous. I would like Go to replace C++ and Java, but false optimism won't make this happen.

by codexon 14y ago

pjmlp 14y ago

> I must have hit a nerve. No, you just got hit with the typical Go activism reply when someone mentions issues with the language.

_ak 14y ago
Issues? What issues? Most complaints about Go are really just "it doesn't contain my favorite language feature", "I heard the GC isn't even precise so it must suck", "it's too immature", "I couldn't get this library to work within 10 minutes so Go sucks", etc. pp., but people are simply unable to point to any actual pain points that hinder productive use of Go.
- ithkuil 14y ago
  I really love go, I try to use it whenever I can. That being said, I still have the feeling that having to rewrite a lot of dummy boilerplate code because of lack of generic collections hinders my productivity. I completely understand that introducing that in the language it's a pandora box, etc etc (not only because of compiler's complexity and compilation speed). But still, I have to find a way around that, being DRY has obvious advantages (although depending too much on obscure magic can be a problem); it's not just a random language feature from my favorite language. I'm trying to see whether https://github.com/droundy/gotgo https://github.com/droundy/gotgo helps
  - _ak 14y ago
    > I still have the feeling that having to rewrite a lot of dummy boilerplate code because of lack of generic collections hinders my productivity. Can you give any concrete code examples including a description what you would have liked differently?
- codexon 14y ago
  With your logic, the same argument could be applied to PHP. The problem is that Go simply doesn't solve anything new. If Go contains your favorite language features but not mine, then why should I bother to use or hype it? If you want lightweight concurrency with GC you could have gone with Scala, Erlang, or Haskell.

_ak 14y ago

> Besides Vitess, what other high profile usage is there at Google? The piece of software that runs on dl.google.com, which serves millions of Chrome updates every day, is written in Go. The problem is: you're asking for Go success stories at Google, even though most of Google's internals will never be published. Why don't you just take a closer look at other companies' success stories and acknowledge them? > Not to mention they offloaded part of the implementation to Memcache because Go wasn't good enough. Huh, what? Using memcached means the technology you use isn't good enough, or what are you trying to suggest? Don't forget that the author of memcached is a core Go developer at Google, so I'd say they know what they're doing.

bobbydavid 14y ago
Can anyone explain why this was downvoted?
- _ak 14y ago
  Because HN jumped the shark and is now basically Reddit in a different color theme.
- codexon 14y ago
  I didn't downvote it, but it was downvoted for a good reason. He didn't spend much effort to understand a simple sentence. http://code.google.com/p/vitess/wiki/ProjectGoals#Why_did_we_choose_go http://code.google.com/p/vitess/wiki/ProjectGoals#Why_did_we... > Go’s existing mark-and-sweep garbage collector is sub-optimal for systems that use large amounts of static memory (like caches). In the case of vtocc, this would be the row cache. To alleviate this, we intend to use memcache for the time being. For a self-described systems level language this is ridiculous. I would like Go to replace C++ and Java, but false optimism won't make this happen.