For example, humans evolved to be social creatures. Interactions with other humans impact our body chemistry in dramatic ways. I want to avoid loneliness, so I selfishly hold relationships with others. I want to hear people say "thanks" to me, so I selfishly give people gifts. I want to be able to be righteous without hypocrisy, so I selfishly stick to my principles.

Just my two cents. There are a lot of different types of desire in the world. Who's to say that UBI wouldn't be in folks' best self-interest?

I find this is effective even if you actually do want them to change their decision. Come in with a compliment, then try to lead them to recognize the flaws in the decision themselves.

In my experience, H.N. comments have a lot of wrong. But when the content is good, it can be truly great.

If they are running multiple Docker containers, the improved efficiency would allow them to run more containers per host computer. Maybe that's what they meant, although it's not really horizontal scaling either.

Having said that, thanks for the interesting digression. You've made me want to try out ipfs.

This is especially bad for Samsung, I think, because it doesn't just affect folks with a Note 7 -- everyone waiting at the gate hears the announcement. Talk about negative brand associations.

[0]: https://www.faa.gov/news/updates/?newsId=86424

A Pi, though, couldn't do well at all, just like you said. If I wanted to build a system like this for myself, I would target an HTPC form factor.

edit: Another possibility, which was explored elsewhere in this thread, would be to keep the listening device "thin", but have the ability to offload the processing to a machine in my LAN instead of one the "cloud".

Applications behave consistently because all state is stored in a single object, so it can't be desynchronized across components. Because all updates use a single function, it becomes easy to track and respond to any state changes by applying middlewares to that function. Things are more testable because all state is available for stubbing, and because the "reducer" is a testable, pure function typically composed of many other smaller, testable pure functions.

Things like time travel become possible because of the purity of the reducing function. Since it's pure, it can't modify the old state object (technically, it can, but it's against the rules). So in theory, we can undo any state change simply by loading the old state object from where it's being stored by some kind of history middleware.

Also, sometimes even just using console.log can cause bugs to appear or disappear. I recently encountered a bug which was almost impossible to diagnose with console.log, because the string returned by the .toString() call didn't correspond to the real object's actual properties. Of course, this is a rare case, but it highlights the benefit of trying different tools!

More to the point, I think that definition is a little dissatisfying. By that metric, I have probably never created any art in my life -- because I'm not an artist with limited-edition work in a gallery. To me, that is unacceptable for a definition of art. Artistry is something more intrinsic to human nature than just being a thing made by an "artist" and put in an artistic context to be admired by hipsters and to confuse people.