There's some other things to keep in mind about Liquid Fluoride Thorium Reactors (LFTRs):
Thorium is a natural impurity found in coal. It has been estimated, in fact, that the thorium in coal would, if used as fuel for LFTRs, generate eleven times the energy that you would get from just burning the coal. And right now, all that thorium is simply wasted in the coal ash, or worse, goes up the smokestack and becomes an environmental pollutant!
Also, due to the higher temperature LFTRs run at, they can directly supply heat to drive the Fischer-Tropsch process to convert the coal that we'll no longer need to burn for electricity into synthetic petroleum. This would allow the U.S. to completely supply all its petroleum needs (especially for transportation fuel) from coal for at least 100 years, and eliminate the need for foreign oil. This, in turn, would allow the defense budget to be cut in at least half, as much of that expenditure is to protect our access to foreign oil. And it also reduces carbon emissions, since, while we're still burning the coal (after it's been transformed into synthetic petroleum), we're not burning the oil it replaced!
None of this requires new technology; we were running LFTRs at Oak Ridge in the 1960's (and they proved their safety by literally cutting power to the reactor systems and going home for the weekend!), and Germany was using Fischer-Tropsch back in World War II. All it requires is some engineering refinements...and, of course, the political will to do it. The latter, sadly, is lacking.
Though she's more famous for The Dragonriders of Pern and The Ship who Sang, I will always have a soft spot in my heart for her Crystal Singer series. Look it up sometime; it's a nice little combination of music, mining, meteorology, and not a little romance.
She has passed for all time between; we accord her a dragon tribute. May she always sing the black, and cut well.
Actually, now that I look at it, the answer would be "no." No MicroSD slot means no nifty bootable-card hacks like you can pull with the Nook Color, and (possibly) the Nook Tablet as well.
The company I work for has a TV in the break room, which is fed by DirecTV. I was in there at the time of the test, and the TV (which was displaying the Discovery Channel at the time, I think) displayed a DirecTV "Emergency Broadcast System Test" card, and I saw the scrolling letters across the screen announcing an EAN for the District of Columbia, which is one of the things that was expected. When it was over, the TV displayed its previous program.
So it looked fine to me, although apparently there were a bunch of problems elsewhere. Ah well, that's why they call it a "test"...
I had one of the PalmOS watches, too; it was called the Fossil Abacus WristPDA. I wore it for a couple years, and stored things like my address book and password file in it. Eventually, it, along with my iPod Nano and Nokia flip phone, was replaced by my iPhone. But I wouldn't mind wearing an Android-based replacement.
Trading is all about the banks taking out the stops.
And the HFT algorithms, in order to do so, deliberately manipulate the prices of shares, by stuffing the channels with quotes for bids and offers that the algorithms have no intention of executing.
Under long-standing law, any pattern of orders intended to manipulate the price of a security, as opposed to actually buy it or sell it, is illegal.
Where are the damn COPS? Where are the indictments, and the handcuffs, and the perp walks? Why aren't there bankster fraudsters currently doing time in federal PMITA prison for this?
Of course, you know the answer. The regulators have been co-opted. The government is looking the other way. And the "little guy" gets screwed. Again.
It is absolutely this. I would go so far as to say that no individual investor has a chance in the markets when going up against these HFT algorithms run by the big banks and trading firms. No matter how good your analysis or how closely you watch the market like a hawk, you're going to be screwed, blued, and tattooed.
And this comes at the same time as The Fed and Chairsatan The Ben Bernank have pretty much destroyed all "safe" investments through manipulation of interest rates, forcing people to turn to the stock market if they want any hope of any kind of significant return on their money...and where they can be fleeced by the HFT algorithms and the bankster fraudsters. Not to mention destroying the purchasing power of those dollars via "quantitative easing" (read: money printing) games.
Probably a good time to invest in precious metals. No, not gold, silver, and platinum. I'm talking steel, lead, and brass...in appropriate forms, of course.
Through several jobs, a number of projects, and at least one marriage, Slashdot has been a constant in my life, keeping me grounded in "who and what I am" always.
Good luck, Rob, and one more piece of wisdom: Life moves pretty fast. If you don't stop and look around every once in awhile, you could miss it. (The words are not mine, as I'm sure you recognize...that doesn't make them any less true.)
Regards,
Eric J. Bowersox - "Erbo"
Professional Java Developer and Geek among Millions http://about.me/erbo
Your mission, should you choose to accept it, is to steal the $5 trillion coin held by the Federal Reserve. If you are captured or killed, the Secretary will disavow any knowledge of your actions. This message will self-destruct in 10 seconds.
Granted. The most extreme example of this is embedded development, which is one of those "corner cases" I referred to where C++ is justifiable and languages such as Java are definitely contraindicated.
Of course, never forget the Laws of Code Optimization:
The First Law of Code Optimization: Don't do it.
The Second Law of Code Optimization (advanced experts only!): Don't do it yet.
That should really have been called "NullReferenceException" but Java baked that mistake in pretty early on, so we're stuck with NPE.
I've also opined that Java really needs to adopt the "safe navigation" operator from Groovy, which acts like the regular "." operator, but, if the left side is null, returns null rather than throwing NPE. In effect, the expression "a?.b" is equivalent to "a == null ? null : a.b". That alone would help eliminate a bunch of the NPEs I see on a regular basis.
Oh, granted, there's no substitute for good, careful design in any language. I just cleared up a problem in my company's massive Java application today which involved an extra object copy being created and then persisted to the database, resulting in a "concurrent modification" error message (as one copy in memory was no longer in sync with the one in the database). Sometimes it can be so easy and painless to create a new object, that you don't stop and ask whether you really should.
But simply due to automatic memory management, there are whole classes of bugs, some of them nasty, in C++ that simply do not exist in Java. (And, of course, Java probably has a few that C++ doesn't have. Perfection is nonexistent. You pays your money and you takes your choice.)
And, while C++ will always necessarily be faster to execute, there's no question that the other three languages will be faster and more straightforward to develop in. (Which, in general, makes them a net win, as programmer time is almost always more expensive than computer time, except in certain corner cases which should be obvious.)
Why? Three words: Automatic memory management.
No more worrying about whether you've allocated the right buffer size for your data...and maybe allocated too little resulting in an overrun screw, or allocated too much and wasted the memory. And no more forgetting to free that memory afterwards, resulting in a memory leak. You can write expressions like "f(g(x))" without having to worry about how the return value from "g" is going to be freed, allowing a more "natural" coding style for compound expressions.
I maintain that automatic memory management, while not great for code-execution performance, is probably the single biggest boon to developer productivity since the full screen-mode text editor. (Not saying "emacs" or "vi" here. Take your pick.)
Granted: You can retrofit a garbage-collecting memory manager onto C++...but that code will rob your C++ code of some of that enhanced execution performance which is probably the reason why you chose to develop in C++ in the first place.
Slashdot Mirror
Actually, two plus two does equal ten...for sufficiently large values of two.
Now, did they list his full, legal name, "Bender Bending Rodriguez," on the ballot?
Thorium is a natural impurity found in coal. It has been estimated, in fact, that the thorium in coal would, if used as fuel for LFTRs, generate eleven times the energy that you would get from just burning the coal. And right now, all that thorium is simply wasted in the coal ash, or worse, goes up the smokestack and becomes an environmental pollutant!
Also, due to the higher temperature LFTRs run at, they can directly supply heat to drive the Fischer-Tropsch process to convert the coal that we'll no longer need to burn for electricity into synthetic petroleum. This would allow the U.S. to completely supply all its petroleum needs (especially for transportation fuel) from coal for at least 100 years, and eliminate the need for foreign oil. This, in turn, would allow the defense budget to be cut in at least half, as much of that expenditure is to protect our access to foreign oil. And it also reduces carbon emissions, since, while we're still burning the coal (after it's been transformed into synthetic petroleum), we're not burning the oil it replaced!
None of this requires new technology; we were running LFTRs at Oak Ridge in the 1960's (and they proved their safety by literally cutting power to the reactor systems and going home for the weekend!), and Germany was using Fischer-Tropsch back in World War II. All it requires is some engineering refinements...and, of course, the political will to do it. The latter, sadly, is lacking.
This is true. "Weyr Search," which is basically the first part of Dragonflight, even won the Hugo.
She has passed for all time between; we accord her a dragon tribute. May she always sing the black, and cut well.
Actually, now that I look at it, the answer would be "no." No MicroSD slot means no nifty bootable-card hacks like you can pull with the Nook Color, and (possibly) the Nook Tablet as well.
I came here to say that, or at least to ask the question: Has the Fire been rooted yet? Is it as hacker-friendly as, say, the B&N Nook Color?
So it looked fine to me, although apparently there were a bunch of problems elsewhere. Ah well, that's why they call it a "test"...
I had one of the PalmOS watches, too; it was called the Fossil Abacus WristPDA. I wore it for a couple years, and stored things like my address book and password file in it. Eventually, it, along with my iPod Nano and Nokia flip phone, was replaced by my iPhone. But I wouldn't mind wearing an Android-based replacement.
Weight has nothing to do with it!
And the HFT algorithms, in order to do so, deliberately manipulate the prices of shares, by stuffing the channels with quotes for bids and offers that the algorithms have no intention of executing.
Under long-standing law, any pattern of orders intended to manipulate the price of a security, as opposed to actually buy it or sell it, is illegal.
Where are the damn COPS? Where are the indictments, and the handcuffs, and the perp walks? Why aren't there bankster fraudsters currently doing time in federal PMITA prison for this?
Of course, you know the answer. The regulators have been co-opted. The government is looking the other way. And the "little guy" gets screwed. Again.
For more information, you'll want to look at Nanex.net's "Flash Crash Analysis" page.
And this comes at the same time as The Fed and Chairsatan The Ben Bernank have pretty much destroyed all "safe" investments through manipulation of interest rates, forcing people to turn to the stock market if they want any hope of any kind of significant return on their money...and where they can be fleeced by the HFT algorithms and the bankster fraudsters. Not to mention destroying the purchasing power of those dollars via "quantitative easing" (read: money printing) games.
Probably a good time to invest in precious metals. No, not gold, silver, and platinum. I'm talking steel, lead, and brass...in appropriate forms, of course.
Good luck, Rob, and one more piece of wisdom: Life moves pretty fast. If you don't stop and look around every once in awhile, you could miss it. (The words are not mine, as I'm sure you recognize...that doesn't make them any less true.)
Regards,
Eric J. Bowersox - "Erbo"
Professional Java Developer and Geek among Millions
http://about.me/erbo
Your mission, should you choose to accept it, is to steal the $5 trillion coin held by the Federal Reserve. If you are captured or killed, the Secretary will disavow any knowledge of your actions. This message will self-destruct in 10 seconds.
I don't want that mama stickin' it in, or anywhere near, the camera, if I can possibly help it.
Wow, you solved a puzzle aimed at 12 year olds. Would you like some cake?
I understand that this offer may not be entirely the truth.
"No one shall engage in unprovoked ganks in Empire highsec, on pain of being CONCORDOKKEN'd."
Of course, never forget the Laws of Code Optimization:
I've also opined that Java really needs to adopt the "safe navigation" operator from Groovy, which acts like the regular "." operator, but, if the left side is null, returns null rather than throwing NPE. In effect, the expression "a?.b" is equivalent to "a == null ? null : a.b". That alone would help eliminate a bunch of the NPEs I see on a regular basis.
But simply due to automatic memory management, there are whole classes of bugs, some of them nasty, in C++ that simply do not exist in Java. (And, of course, Java probably has a few that C++ doesn't have. Perfection is nonexistent. You pays your money and you takes your choice.)
Why? Three words: Automatic memory management.
No more worrying about whether you've allocated the right buffer size for your data...and maybe allocated too little resulting in an overrun screw, or allocated too much and wasted the memory. And no more forgetting to free that memory afterwards, resulting in a memory leak. You can write expressions like "f(g(x))" without having to worry about how the return value from "g" is going to be freed, allowing a more "natural" coding style for compound expressions.
I maintain that automatic memory management, while not great for code-execution performance, is probably the single biggest boon to developer productivity since the full screen-mode text editor. (Not saying "emacs" or "vi" here. Take your pick.)
Granted: You can retrofit a garbage-collecting memory manager onto C++...but that code will rob your C++ code of some of that enhanced execution performance which is probably the reason why you chose to develop in C++ in the first place.
All I know is, if I ever get an iPad, I'm getting this case for it.
For more on this story, we switch you now to our special correspondents, the Flying Pigs.
More like "Houston...FUUUUUUUUUUU-"
"Temporal mechanics always gave me a headache back at the Academy." - Kathryn Janeway