HN user

trisiak

84 karma
Posts1
Comments27
View on HN

The article makes a point that contemporary hunter gatherers are not living the life like their ancestors. "Modern" cultures displaced them into much less favorable environments.

Can you provide some examples of frameworks with such pattern? I actually have never seen it in any of the Python or Go web applications that I had a chance to work with.

Best of HN 2020 6 years ago

Pure speculation but could it be a network effect? I frequently visit websites that were shared by coworkers and friends over text communicators that they originally found on HN.

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.

No reason to be frustrated. Things are almost never right or wrong, particularly in complex science.

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.

Is the EU also going to come out with the "Right to breathe" and the "Right to go to the bathroom when you need to"?

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.

Isn't that the same in practice?

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.

Practices like that are directly against the spirit of data portability under GDPR and CCPA. What's protecting Spotify here is that the user's data is accessed through an API not considered for that privacy control use case.

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).

I too suffered from wrist pain and fatigue in the past. The experimentation with different layouts helped a little but it felt like micro-optimization. What actually resolved the problem was switching to an unorthodox ergonomic keyboard where none of the keys required straining or unnecessary effort (kinesis advantage, using a different one these days). Also, most common problems were caused by placement of special keys (shift, ctrl, backspace, enter) and that's not something colemak, dvorak or their friends seem to be addressing.

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.

The distribution of numbers is not uniform across the 0..googol here. The implementation first chooses the length of the number, then fills in the digits. This makes it biased towards smaller numbers.

Does it still have the same optimal strategy as for uniform generation?

The main point of the article is not that CF is evil and is now getting all your DNS data; it is that CloudFlare gets that data AND none of those that had access to it already are going to lose it after you migrate to DoH.

I meant finding it in the context of a coder who writes a function. It's hard to identify which expression and statements can cause exceptions and effectively short-circuit your function. In contrast to explicit errors-returned-as-values.

(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.)

The similarity in both needing to have stack trace does not make them very alike yet. They serve similar purpose and for that purpose the stack trace serves value to the developer.

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.