Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
groestl
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
72 ms
·
961.
▲
by
groestl
8y ago
The parent is correct. Returns also unwind the stack. > One important benefit of Go's error handling pattern is readability I beg to differ, Go's approach is similar to checked exceptions, Java's original sin. And just lik
962.
▲
by
groestl
8y ago
Easy, just assume it throws. That's the case anyway. Thanks to panics, even in Go. Edit: Also, there is no parallel control flow. Languages with exceptions have union-type return values, and every statement is implicitly followed by th
963.
▲
by
groestl
8y ago
> I've heard from many devs that Go was the reason that made them appreciate proper error handling. I agree that in some way, this is actually a good reason to support Go's tedious way of handling errors. Yet, it's akin to
964.
▲
by
groestl
8y ago
We hit that HTTP request limit as well, and (driven by a discussion with Google support) migrated our backend away from the REST-based Google Cloud Datastore API to the internal (ApiProxy-based) Appengine API. Reduced the latency as well. I
965.
▲
by
groestl
9y ago
Just be the guy who says "oh a POST is fine" first
966.
▲
by
groestl
9y ago
Idempotency might be necessary for GET calls, but it's not sufficient. Imagine he had two separate GET calls (opened/closed): the author would still have the same problem. Browsers assume GET to be safe (non-mutating), and safety
967.
▲
by
groestl
9y ago
What Facebook acquired from their users was "expressed consent", which is notoriously easy to get using dark UI patterns. But the technical community has been using "informed consent" in their definition of malware for a
968.
▲
by
groestl
10y ago
Funny, just a few days ago I watched a TEDx talk about this by a computer scientist on the team. Maybe you enjoy it as well: https://www.ted.com/talks/katie_bouman_what_does_a_black_hol...
969.
▲
by
groestl
10y ago
> Sorry, but robbing Peter to pay Paul does not strike me as a viable long term strategy either. Of course that's not a viable long term strategy. The viable long term strategy is Peter giving away decent food and shelter to Paul fr
970.
▲
by
groestl
10y ago
Exactly. As another user in this thread pointed out, people tend to apply microeconomic thinking to macroeconomic problems. They think in monetary terms, but money is irrelevant in this context. What matters is produce, the capital to produ
971.
▲
by
groestl
10y ago
Maybe I did not phrase it clearly enough, but I know that there is plenty of work, just not paid work. That's why I used the word "jobs". Companies leave the demand for mental health on the table, because the metally ill don&
972.
▲
by
groestl
10y ago
Where do the jobs for the elderly come from, if even young, healthy people are gradually priced out of their jobs by technology and automation? Right now, good jobs are replaced by bad, underpaid ones. Desperate people are serving burritos
973.
▲
by
groestl
10y ago
Exactly. Why waste the time to fabricate a collision when all you have to do is "accidentally" commit exploitable code? At least then you got plausible deniability.
974.
▲
by
groestl
10y ago
Thank you for these reports! @"good government style reaming", I just wanted to add that interestingly, a government (at least a democratic government) operates exactly the opposite of Google/Facebook. By which I mean that th
975.
▲
Announcing YoLang: A zero-purpose programming language
(yolang.org)
7 points
by
groestl
12y ago
|
1 comments