4,952 karma · joined July 15, 2015
That doesn't seem right. Tons of travel content existed before he got popular. Endless summer wasn't for women
His really early ones were kind of rough. Like you could see he was still figuring it out. There was one episode where he just narrated a lonely planet guide.
Would be cool if python had a pipe operator though.
The back ticks in ruby is pretty ergonomic too. Wish python had a simpler way to run commands. Kind of tedious to look up subprocess run arguments and also break things up into arrays.
Same for sql, do you really context switch between sql and other code that frequently?
Everyone should stop using bash, especially if you have a scripting language you can use already.
It's like saying python is complex becasue you have metaclasses, but you'll never need to reach for them.
I would have guessed linters would have complained about what's being suggested there. Is the something special about var: _ thing that avoids it?
exceptions vs returned errors i think is a different discussion then what im getting at here.
The error type in go is literally just a string
type error interface { Error() string }
That's the whole thing.
So i dont know what your talking about then.
The wrapped error is a list of error types. Which all include a string for display. Displaying an error is how you get that information to the user.
If you implement your own error, and check it with some runtime type assertion, you have the same problem you described in python. Its a runtime check, the API your relying on in whatever library can change the error returned and your code won't work anymore. The same fragile situation you say exists in python. Now you have even less information, theres no caller info.
Go's wrapping of errors is just a crappy exception stack trace with less information.
The exceptions from something like open are always pretty clear. Like, the files not found, and here is the exact line of code and the entire call stack. what else do you want to know to debug?