Now that I think about it, are there any color schemes or extensions that highlight the error handling logic differently so that one can better focus on the “main” logic flow of the code while the error handling logic is still there?
So about 5% of the error checking code is about handling the edge cases, where we are very much interested in what the error actually is, and need to handle those conditions carefully.
If you discard that as "error handling noise", you're in for a bug. Which is, by the way, perhaps the worst side-effect of verbose, repetitive error handling.
Apropos syntax highlighting: many themes in regular use (certainly most of the defaults) choose a low-contrast color for the comments. The comments are often the most important part of the code.
I would love something like this, and if it exists, I've not come across it. Offloading a way of differentiating error handling syntax vs. normal code to the IDE seems like a nice way of handling this issue.
HTML+CSS, converted to PDF via the Save As PDF feature in Firefox. (Or the same could be done with other browsers, but this one apparently comes from FF.)
The objection in TFA was ecological damage due to de-oxygenation of the water. They don't mention boats as a problem so I'd guess that's taken care of?
As for the size of the laguna, they're talking about walling the whole thing off so some circulation pumps shouldn't be too much of a stretch. Alternately they could install some kind of bubbler system (like a giant version of a fish tank air pump) to keep the water aerated in situ. Again, it's not going to be pocket change but it's an option.
