Those animals got all of their carbon from the fields they were standing in. If the animals hadn't been there, that same carbon would have been turned into CO2 by organisms like insects or fungi. The overall amount of CO2 released would have remained almost exactly the same.

Yet by my calculations, the train has enough kinetic energy to lift itself over 3100 feet up into the air. So the depth of any ditch isn't really going to help.

I assume it's "locked" into the track, but at these speeds the entire train could probably disintegrate into confetti if it hit a solid enough obstacle, so it's not impossible for the majority of the mass of train to come off the rails.

Hardly. Cosmonauts returning from Mir after only one year in space could barely function once they returned to earth. I kind of doubt that anybody would physically survive 10 years in zero-G, even assuming they've survived the long-shot odds of no fatal spacecraft malfunctions in 10 years.

Not to mention that they would gone bat-shit insane by that time, after they realized that they've sat in a tiny tin can eating stale cat food and being blasted by cosmic rays for over a decade just so they get a sample of some crappy small-time comet; a job that could be easily done by a robot.

Due to the inherent design of C/C++ header files and their "compile units", building any large project in C++ takes almost forever. The work to build grows significantly more than linearly with the number of source files.

Many things in C++ feel very "brittle" largely due to the limitations of its type system and generics.

C++ reference counting is better than fully manual memory management, but still often requires careful attention to "ownership" issues, leaving a risk of leaks or segfaults.

Most recommedations from the experts advise against using most of the actual features of C++ because they are so poorly conceived, poorly supported, or cause safety or compatibility problems. Best to stick with a bare-bones subset that's not very satisfying.

Many of these problems were addressed by languages such as Java and C#. However those both require a heavyweght "virtual machine" runtime. The nice thing about Go is that it creates self-contained executables that run without needing to install anything special on the target machines (at the cost of the executables being larger than most people are used to).

Congress has been fiddling with DST since it was invented. If you were somehow under the impression that congress would never change DST again while you evaluated equipment for purchase, then you deserve what you get. I'm not going to give up a couple of hundred hours of useful daylight per year to help you compensate for your short-sighted technology buys.

Your job doesn't have any set hours? You're the one who sounds like a part-time burger flipper.

I've been an adult for decades, and I've never met anybody who is not a mother-in-law that regularly goes to bed at 9pm.

The earlier you go to bed, the *less* of a problem it is. But most people go to bed somewhere around midnight or a little before. Having the sun come up before 4:30am in much of the country would just be silly, IMO.

Window treatments are generally not that effective unless you buy expensive and ugly "total blockout" versions. Why should I have to do that just to appease DST whiners?

You don't think that bright sunlight streaming into bedrooms for an extra hour all summer won't screw with peoples' sleep cycles even more?

Before clocks, people probably naturally implemented daylight savings time by waking up at sunrise. Now that our whole lives are tied to external schedules, not having DST is more artificial than having it.

Nobody in their right mind is going to wake up one minute earlier than necessary before work. And if they did, they'd have a looming deadline to get to work right as they start to get into whatever morning activity they're doing, which would negate much of the value of that time block.

People worry about a few extra heart attacks once per year with DST. What about entire neighborhoods being woken up on mornings where some jackass early-riser thinks that the extra morning daylight hours would be a great time to mow their lawn and blow leaves? Who is going to count the heart attacks caused by that?

Other people want to stay on permanent DST. Who is going to tabulate how many kids get run over going to school in pitch black mornings?

DST as it's currently implemented works just fine. Keep it as it is.

Do they allow packages to be ranamed? Then changing only 5 bits woudl rectify the situation.

If they just leave the code as-is, but change the name from "ownCloud" to "pwnCloud", then the actual functionality of the package would be clear to everyone.

They weren't able to do it back then, either.

Any large order had an almost 100% chance of having an arithmetic error. It was always unfathomable to me how more than a century after the invention of the cash register, a multi-billion dollar company could predicate all of their income on high school students' scribbling. Not to mention having to wait in line while all these errors were tediously generated by the staff then checked over by irate customers.

It was a great thing when McDonalds finally dragged themselves into the 19th century.

An additional advantage to those signs is that in a dystopian future, the terrorists are usually the good guys. The info will help direct those good guys to where they can find materials helpful in the fight against evil governments.

It's not cheating if it's part of the strategy of the event. See also: NASCAR, speed skating, bicycle racing, etc. It just means that in addition to raw speed, the runner needs to effectively manage the interactions with other runners.

At any rate, this arbitrary milestone would have been achieved long ago if the wavelength of light emitted by exited caesium 133 atoms were only a tiny fraction of a percent longer.