> You may as well use exception handlers if you're going to go there. I didn't know about this trick, thanks for sharing.
Yes, and all are equally offensive to the average Go hater, all of them have NULL, and all of them have terrible error handling. It's not "argument from popularity", it's "argument from success". Some things succeed.…
>Abstractions make large systems easier to understand, not harder. I raise you AbstractSingletonFactoryProxyBean.
You can do something like this: type errHandler struct { err error } func (eh *errHandler) getFirst() string { // stuff if err { eh.err = err } return result } func (eh *errHandler) doWith(input string) string { if…
How come a reinvention of a 30 year old wheel is more successful and popular than pretty much every language that attempted to evolve the wheel during that time? "It's because people who like Go are stupid and companies…
[flagged]
Pretty much every reputable computer scientist has been saying for the last 70 years that the most important thing in the entire world is simplicity and ease of understanding.
Compactness is in the eye of your beholder. You might have the eyes of a spider, but I have the eyes of a large orc.
"bad" ideas? Really? Are you so sure? Are your ideas really any better? What language have you made that has seen more success than Go? Clearly if they did such a bad job it would be easy for you to fix it all up and…
> Do this call value, err := function() > if there is an error return it if err != nil { return err } > otherwise give me the value // rest of the code goes here
So you would prefer to write match result => error instead of if err != nil? Excuse me for not being convinced that this isn't just fussing over syntax.
More like you ignore the existing work that Go itself is built on.
More than one person designed the language than Pike, you know. He's retired. Maybe you can find another member of the devteam to pick on?
I don't really agree. I find Iota perfectly serviceable.
> You may as well use exception handlers if you're going to go there. I didn't know about this trick, thanks for sharing.
Yes, and all are equally offensive to the average Go hater, all of them have NULL, and all of them have terrible error handling. It's not "argument from popularity", it's "argument from success". Some things succeed.…
>Abstractions make large systems easier to understand, not harder. I raise you AbstractSingletonFactoryProxyBean.
You can do something like this: type errHandler struct { err error } func (eh *errHandler) getFirst() string { // stuff if err { eh.err = err } return result } func (eh *errHandler) doWith(input string) string { if…
How come a reinvention of a 30 year old wheel is more successful and popular than pretty much every language that attempted to evolve the wheel during that time? "It's because people who like Go are stupid and companies…
[flagged]
Pretty much every reputable computer scientist has been saying for the last 70 years that the most important thing in the entire world is simplicity and ease of understanding.
Compactness is in the eye of your beholder. You might have the eyes of a spider, but I have the eyes of a large orc.
"bad" ideas? Really? Are you so sure? Are your ideas really any better? What language have you made that has seen more success than Go? Clearly if they did such a bad job it would be easy for you to fix it all up and…
> Do this call value, err := function() > if there is an error return it if err != nil { return err } > otherwise give me the value // rest of the code goes here
So you would prefer to write match result => error instead of if err != nil? Excuse me for not being convinced that this isn't just fussing over syntax.
More like you ignore the existing work that Go itself is built on.
More than one person designed the language than Pike, you know. He's retired. Maybe you can find another member of the devteam to pick on?
I don't really agree. I find Iota perfectly serviceable.