Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: failure (Score 1) 113

by FalseModesty (#41915491) Attached to: MIT Slows Down Speed of Light In New Game

This was a bad demonstration of relativistic effects. All it really does is demonstrate the Doppler effect, and it does that poorly. People are evidently not warm, because they do not glow when infrared light becomes visible. Chimneys do, but so do shadows under roofs.

The huge mushrooms emit what, gamma rays? They emit light that is visible even when enormously red-shifted.

There is no Sun or sky. No campfires. No warm machinery. No radios. No flowers with UV patterns. Nothing familiar that will illustrate something interesting about the Doppler shift and the world of invisible light.

It's a nifty idea, but finish it before releasing it.

Comment: Re:It depends on whatcha mean when you say style (Score 1) 479

by FalseModesty (#41794795) Attached to: Does Coding Style Matter?

Seriously? You are reading the code, fixing bugs, and you find formatting problems. So you back out your half-complete changes, fix the formatting, commit that change, then re-apply your fix-in-progress? You actually do that? Of course you don't.

The better policy is that code must be formatted correctly when it is committed the first time. Which is why we have style guidelines in the first place.

Coders should spend their time looking at the code, not getting distracted by style variations.

"Who alone has reason to *lie himself out* of actuality? He who *suffers* from it." -- Friedrich Nietzsche