Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


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: Re:And the Spinning BeachBall of Death? Sad Mac? (Score 1, Insightful) 61

by Brett Buck (#49211363) Attached to: Classic Mac Icons Archive Bought By MOMA

I have used Macs since they existed, and I never once saw the Sad Mac, aside from looking it up, or seeing it in documentation. The spinning beach ball was also exceptionally rare until OS X came along, now you do see that one occasionally.

    On "IBM machines" AKA DOS machines , I have seen xxx failed, Abort, Retry, Fail? almost incessantly. Not artistic, not particular memorable, aside from being drilled into one's head like "Polly Want a Cracker?" is for parrots.

Comment: News? (Score 5, Interesting) 33

People have been launching sounding rockets into the aurora borealis for something like 60 years - in the many hundreds, if not thousands. The facilities in AK and Canada are far and away the most active sounding rocket sites in the world because of it.

    How is this news?

Comment: Re:What's the term for a prophylactic prediction? (Score 1) 677

by Brett Buck (#49041639) Attached to: Empirical Study On How C Devs Use Goto In Practice Says "Not Harmful"

Whether he was right or wrong, people have taken his statements, as with most religious zealots, to the ultimate ridiculous end.

      I heard the capper in about 1988 or so, when one of our customers asked, during a code review, if an unconditional branch in assembly code wasn't just like a GOTO, which was prohibited.


Comment: Re:why? (Score 1) 677

by Brett Buck (#49041609) Attached to: Empirical Study On How C Devs Use Goto In Practice Says "Not Harmful"

You win! I was showing some newbies an example of that yesterday. With a lot of error checking, and indenting that Wirth would have approved of, the inner statements in the deepest loop wouldn't have fit on the screen.

      The alternative chosen was *multiple subroutine exits*, which is arguably much worse than a few GOTOs.


Comment: Re:Yeah! (Score 1) 282

by Brett Buck (#48952959) Attached to: NASA Looking At Nuclear Thermal Rockets To Explore the Solar System

That's compared to a few hundred pounds for an equivalent chemical rocket. The point of post you are replying to is absolutely correct, it only makes sense if the rocket using it is large and carries a large amount of propellant.

      There are effectively two factors in rocket design - the engine ISP and the mass ratio. The mass ratio is a measure of how much propellant is carried VS the dead weight (engine, tanks, payload). Those two things can tell you the velocity change of the rocket (see: "rocket equation"). Note that you have to recognize that the ISP and exhaust velocity are one and the same to make sense of it.

  The ISP is twice as good as a chemical rocket, but the dead weight is very high, too, so for this to make sense, you need a large amount of propellant. The difference between 250 lbs (chemical rocket weight) and a few thousand (practical lower end of the NTP and associated shielding, etc) could be critical.

    For example, using hydrogen as a working fluid increases the ISP (the lighter the exhaust products, the better) but reduces the mass ratio because the density is so low, the tanks have to be gigantic and therefore heavy. reducing the mass ratio. If it used Xenon, it might have lower ISP but the dead weight would be smaller due to much smaller fuel tanks. It's a trade-off, and NTP engines don't care very much what fuel they use.

    Someone has already figured all this out, there was a perfectly sound design for a rocket upper stage using a NERVA engine, I would suggest that as a point for further research.

Old programmers never die, they just branch to a new address.