84 karma · joined April 9, 2018
Other possibility, do you have a gaming mouse with 1000Hz polling rate configured?
Obviously, not all people vote or comment either so that's a second multiplicative factor.
Finally, causation != correlation, which most likely is your point, e.g. things on HN already spread from somewhere else.
In this case, based on another comment above about "emergency procedure" having multitude of meanings, you're most likely wrong in that the paper has a rebuttal to the top post. The hypothesis then, is that the actual urgency of surgeries is not controlled precisely enough to state that they cannot affect the measurement.
Yes, when it becomes a practically accepted norm to violate that right. Is your point that government is overstepping the bounds, or that this type of right does not deserve protection? Or is it just about the semantics and definition of the word "right"?
> Rights are no longer something innate to all humans, they are something that the government gives to you when it wants.
I always thought that the humanity creates communities, countries and their governments to protect those rights, among other things.
You get customers by being nice to them. Being nice to customers means competitive pricing, high quality support, good documentation, easy integration, etc. It's all driving towards the same goal.
A good reading that covers this very topic really well: https://www.joelonsoftware.com/2016/12/09/developers-side-pr...
In principle, a tool for transferring of user's data could be operating on a GDPR/CCPA data export that has to be available for all Spotify users in California and EU. Those are just not exposes as easy-to-use APIs (yet).
Can you offer a source? Asking for a tall friend.
I see analogy to guitar playing here. No matter how well you figure out finger positioning for a complex passage, you won't be playing with ease unless your elbow, wrist and spine are also positioned properly.
Does it still have the same optimal strategy as for uniform generation?
Grouping & capturing parentheses can stay. It's only the back-referrences that you need to remove.
(Panics of course can cause similar thing in Go but that's the reason why they should rarely be recovered and not used as a value propagation mechanism.)
Returns go straight up the stack only if you choose them to. Caller doesn't have to propagate errors and return immediately, it can hold onto them and/or process them in the natural place they occur, they are just values. The returns from your function can be found with "grep return".
Exceptions, by default, break the natural control flow unless you wrap everything with try/catch. Even then, a lot of constructs won't be very natural and you really will have to get out of your way to identify the source of the exception, which very frequently is more important than it's type.