3 ms·

You've read a lot of very bad Go code then, that doesn't follow any of the established practices for it. Your list there is almost a primer of "what not to do

You've read a lot of very bad Go code then, that doesn't follow any of the established practices for it. Your list there is almost a primer of "what not to do in Go", and is certainly not representative of the Go code in e.g. the standard library. I sense some frustration about the language... what happened to make you so anti-Go?

pjmlp 7y ago
You mean like this standard library code? https://go.googlesource.com/proposal/+/master/design/go2draft-error-inspection.md https://go.googlesource.com/proposal/+/master/design/go2draf... > I sense some frustration about the language... what happened to make you so anti-Go? Go is C with GC and bounds checking, aka Limbo reborn with some Oberon-2 influence. Already much better for our IT safety than sticking with C, still I kind of expected Google capable of producing Swift, Rust or TypeScript level of language design, given their pile of PhDs.
- deleted 7y ago
  [deleted]
- marcus_holmes 7y ago
  that's not standard library code? that's a link to one of the few thousand proposals for changing Go error handling... I'm not sure what you're trying to say here... I think keeping Go this simple was an extremely hard thing to do for the designers. I don't know what the intentions were for Swift or Rust, but the Go team were always pretty straightforward that what they wanted was a safer C to write servers in. I think we all agree that they achieved that.
  - pjmlp 7y ago
    Apparently you didn't bother to read it.
boomlinde 7y ago
> I sense some frustration about the language... what happened to make you so anti-Go? That's an utterly pointless derailment.
- marcus_holmes 7y ago
  true, but I was curious
flavio81 7y ago
>I sense some frustration about the language... what happened to make you so anti-Go? Why makes you think everybody should be uppity and approving about Golang? Some of us feel is a step in the wrong direction.

pjmlp 7y ago

You mean like this standard library code? https://go.googlesource.com/proposal/+/master/design/go2draft-error-inspection.md https://go.googlesource.com/proposal/+/master/design/go2draf... > I sense some frustration about the language... what happened to make you so anti-Go? Go is C with GC and bounds checking, aka Limbo reborn with some Oberon-2 influence. Already much better for our IT safety than sticking with C, still I kind of expected Google capable of producing Swift, Rust or TypeScript level of language design, given their pile of PhDs.

deleted 7y ago
[deleted]
marcus_holmes 7y ago
that's not standard library code? that's a link to one of the few thousand proposals for changing Go error handling... I'm not sure what you're trying to say here... I think keeping Go this simple was an extremely hard thing to do for the designers. I don't know what the intentions were for Swift or Rust, but the Go team were always pretty straightforward that what they wanted was a safer C to write servers in. I think we all agree that they achieved that.
- pjmlp 7y ago
  Apparently you didn't bother to read it.

boomlinde 7y ago

> I sense some frustration about the language... what happened to make you so anti-Go? That's an utterly pointless derailment.

marcus_holmes 7y ago
true, but I was curious

flavio81 7y ago

>I sense some frustration about the language... what happened to make you so anti-Go? Why makes you think everybody should be uppity and approving about Golang? Some of us feel is a step in the wrong direction.