GRBs clearly haven't prevented life in *our* galaxy, so the Fermi Paradox still stands.

The caluculations probably rule out life in the core of our galaxy, but systems further out would be exposed even less often than ours is. And even though GRBs can periodically sterilize a planet, their directionality means that one burst would not likely sterilize all the planets in an intercellar civilization simultaneously.

So, to modify what someone said above, we can add another term to the Drake equation, but this doesn't do much to answer Fermi.

That you know of. Besides, I'm sure you've had many that you've caught during the standard code -> compile -> run -> segfault -> debug cycle, but the more subtle ones are harder to trigger.

Depending on what the code is doing and what kind of legacy cruft you're dealing with it's not always trivial.

More likely the other devs feel like it's bad form to drag the names of past contributors through the mud in public. Particularly when the reviewers missed the bug as well.

I'm pretty sure it was implied that P(snowstorm) is high enough to make the cost/benefit rational.

Unless of course you think his comment would be better off at 4 times the length, detailing all of the obvious common sense assumptions he made.

> Inline specifically means "export this as a weak symbol".

Oh gee, and here I thought it meant merge basic blocks. Do you know _anything_ how C++ compilers even work??

>> I can chose between Microsoft's __inline or GCC god-awful __attribute__((always_inline)) syntax.
> Yes, but why are you trying to do that? You're fighting the optimizer and you're almost certain to lose.

You love to constantly make incorrect and incomplete assumptions.

1. I want to write ONE directive not clutter my code up with hacks PER compiler. _Why_ do standards exist ? To make everyone's live _easier_.

2. Gee, why do things like _Profiling_ exist. The *compiler* doesn't have access to *run-time* performance. The optimizer is dealing with a _subset_ of data. It doesn't know the "function temperature".

But go on keeping making excuses. You really don't have a clue.

Sadly that's an accurate summary of the problem caused by First-Past-the-Post voting.

One solution is run-off voting or the Alternative vote.

https://www.youtube.com/watch?...

what with the rabble's concerns boiling over and impinging on the fringes of their attention.

Sorry... I was going for the joke and didn't pitch it very well. My actual views are more like yours.

As for the reality of the subject matter, I would borrow the concept of "probably approximately correct" from machine learning, and give it a 90-95% chance of being ~80% correct. (The 80% is lower to allow room for some more big discoveries like inflation.)

Unfortunately, people will be (hopefully) studying this for thousands of years on top of the <100 we have so far, and none of us will live to see how it turns out in the long term.

And I'm guessing that the publishers who use region codes cry like babies whenever governments impose artificial barriers to free trade.

I always heard it as: "Fool me once, shame on you; fool me twice, shame on me."

And of course, the word of choice usually wasn't "fool".

(Is this really a regional saying?)

> they lose their IP to someone, and the name Ubisoft becomes a curseword...

You mean Ubisucks already isn't? :-)

/me ducks

When companies can "effectively" just "buy laws" (and/or Politicians) corruption knows no bounds for price gouging.