mbar84

I still find it worthwhile to point out when somebody uses a jargon term from an academic discipline, so they maybe can leave the battlefield and its senseless slaughter and instead and chose some other formulation.

> A market failure occurs whenever the individuals in a group end up worse off than if they had not acted in perfectly rational self-interest. Such a group either incurs too many costs or receives too few benefits.

> Even though the concept seems simple, it can be misleading and easy to misidentify.

> Contrary to what the name implies, market failure does not describe inherent imperfections in the market economy

> Additionally, not every bad outcome from market activity counts as a market failure.

As I say, I think he's using it in a very much more colloquial manner: "I don't like the outcome of the market process", which is fine.

I personally would not use this term, just as I would not use e.g. "to beg the question". I wonder if this phenomenon has a name, along the lines of "euphemistic treadmill".

Wrt your first question: The best argument against making energy more expensive is the same argument as it was 100 years ago:

If you use energy now, you build a more prosperous civilization for the future. Your grandchildren may have to deal with a warmer climate, but they will be much better able to do so than if they were more poor.

This argument stands and falls with your evaluation of the benefits of using more energy, the costs of a warmer climate and how you weigh these against each other.

I imagine this might be quite useful to understand data-flow, but I worry that it would be tedious to manage the connections via positions during development.

It would be cool to have an auto-format/auto-layout: - data flowing left to right - draw pipes like yahoo pipes used to - minimize crossing pipes.

When in the programming loop, could the connections be established automatically via references? Name each output and then reference it somewhere else, which implicitly establishes the connection. Then click "auto-layout" (or just hit save) and as Steve would say "BOOM".

Bonus: if you collapse a box, it becomes a black box.

At this point I think it's perfectly fair to start with the assumption that a new Crypto is a scam and it needs to do the legwork to show that it isn't. To claim that a blockchain (the most ludicrously inefficient data-structure ever devised) can scale to a billion users is an outrageous claim. The technical means they found overcome this problem should be front and center in their documentation.

Presumably you've come across this question in your four years of development and would have exact numbers (perhaps not for my chosen value of tx/sec) already at hand. The fact that we're three comments deep into this, leads me to believe you are dancing around the question.

Should we refrain from giving feedback before we have fully articulated the principles by which we would like our code to be written? What about the abundance of tacit knowledge that we can only hope others to learn by osmosis?

Conspiracy theory: Tesla wants to show how bad the system is early on to raise public awareness and make people drive more cautiously around teslas.

Add to that, back then Microsoft had no drive to move the web platform forward. IE was not getting better, which is why it was eventually eclipsed by Firefox and later Chrome.

Let's write a manifesto.

In financial terms, such cascades are typically mopped up by central banks through dilution of the money supply and/or taxpayer financed bailouts.

Long story short: more debt means more risk of a financial crisis.

p.s. I think it is not helpful to use terms such as "our own", "ourselves" when trying to understand these issues.