I don't know about everyone else, but I find it *immensely* helpful to write debugging statements without indentation. This makes it so that they stand out from the normal statements among which the debugging statements are inserted. This is the reason I won't even consider using Python.
Just stick "# XXX" comments around your debug code. Many editors automatically highlight XXX so prominently that it's just as easy to spot as unindented code.
Now, all you Python-indentation-style lovers, consider how you would code this kind of Go initializer:
(This declares the variable 'arr' as a slice of slices of ints and initializes the variable.)
You mean, like:
arr = [[1,2,3][4,5,6]]
What's the problem?
The U.S. navy for instance had their first big encounters in fighting piracy (those at sea, not the intellectual property one). And it wasn't just the Pirates of the Caribbean. Much more important was the fight against the piracy in the Mediterrean. Pirates there, mostly operating from the northern coast of Africa, would not just capture the ships and make booty. They would capture the people also and sell them into slavery. Even U.S. citizens were captured and sold into slavery in northern Africa, and through the whole of the Osman Empire. And how does a fleet operate in sea waters far away from their home coast without any agreements with the states and kingdoms bordering to said sea waters? And be it only for the fleet to be free to get into an harbour and replenish their water and food, repair their ships and buy spare parts. And this was just the first half of the 19th century we are talking about!
You seem to totally underestimate the amount of entanglement you need to get even basic trade routes working.
Battling the entanglement is fighting windmills. And disentanglement is wishful thinking. All you can do is trying to get the entanglement into clear structures.
And the process of splitting water into Hydrogen and Oxygen is well-understood: You just take an anode and a cathode and put them into water. As soon as you connect both to an electric energy source, Hydrogen bubbles will rise at the cathode, and Oxygen bubbles will rise at the anode. This process is called electrolysis of water. The Hofman voltameter was already invented 1866 -- 150 years ago. If you catch the Hydrogen at the cathode, you can store it and later use it for a fuel cell. The amount of energy needed is also easily calculated. The potential difference between anode and cathode should be 1.23 Volts, and the amount of Hydrogen you gain is directly proportional to the amount of charge you transfer between anode and cathode.
There are four of them, not just the Third. And also heat (Q_in, Q_out) is a form of energy, albeit not a very usable one.
I was talking about the First Law of Thermodynamics: U_system = Q - W.
One way to put it is: In the case of a thermodynamic cycle of a closed system, which returns to its original state, the heat Q_in supplied to the system in one stage of the cycle, minus the heat Q_out removed from it in another stage of the cycle, plus the work added to the system W_in equals the work that leaves the system W_out.
Another way to put it is the Law of the Conservation of Energy.
If we increase the energy of a system consisting of Hydrogen and Oxygen by separating molecules of water, we need the same amount of heat and work (Q_in + W_in), as we get when we reduce the energy of the system later by putting Hydrogen and Oxygen together (Q_out + W_out). We can do this by burning the Hydrogen, but then (as you rightly state) we only get 45% back as W_out, everything else leaves as heat Q_out.
As of today, we have fuel cells that increase W_out (as electrical output) up to 70% (SOFC, Solid Oxid Fuel Cells), so only 30% gets converted into heat.
"It doesn't much signify whom one marries for one is sure to find out next morning it was someone else." -- Rogers