That's my point of production cost vs. price. The article stated that currently it costs about $8000 to manufacture about 10kW worth of panels. The new process cuts it down to $4000. However, the current price is about $25000. If all the saving is passed on to the consumer, that would only cut it down to $21000. But you have to factor in capital investments, etc. so most likely you'd save maybe $2000 out of the $20000-$30000 for an installation. That's still 10%, but much less impressive than the 50% that the article seems to imply.
The price ($0.40/W) is the production cost for the PV panel. So, if you want to install, say, a 10kW panel on your roof, the solar panel itself would cost about $4000 to manufacture (as opposed to $8000 by other processes). How much it will cost you, however, still depends on market price, installation and infrastructure cost (batteries, inverters, switches, etc.)
Now, a quick search shows that current panels sell for $250 for a 100W (or $25K for 10kW). And a whole system (< 10kW) is somewhere in the $20-$30K range. What that shows is most of the manufacturing cost of the panels is only a part (30%) of the whole. If all of the saving get forwarded to the consumer, you would see that the the cost might drop about $4K. So basically it'll take 16+ years instead of 20+ years to pay for itself.
After 25 years, you replace the panels and repeat the process, maybe at half the price:)
It is pretty obvious that electronic voting requires both anonymity (to remove fear of retributions) and accountability (to remove fraud).
About the only way to do that is to issue each person to have a pass-phrase coupled pair of electronic "vote cards" that is non-identifying. It would require the present of both cards and the pass-phrase to vote. If you lost one card, you can use the other (plus the pass phrase) to invalidate the lost card (and any recently casted votes.) If you lost both cards, you are SOL. No vote for you.
So, you just can't have a reliable electronic voting system.
With Windows XP going away, in a few years you might be looking for an old box to run your favorite program. In another few years you might be completely out of luck. Even further out, what if Microsoft went bankrupt (or bought by Apple, Google, RedHat, whoever) and their OS division is shelved?
Projects like ReactOS, Wine, DOSBox, etc. allow you to have another possible path in that uncertain future. Your program might not work out-of-the-box, but you have the source to tinker with and try to get it to work.
That is probably the same reason for running Wine on Windows, which is probably better than running an old program within a virtual machine.
Soon enough, you will probably run all of your programs in a browser anyway. But I digress:)
The biggest issue I have with the mirror less / micro four-third camera families is with ergonomics. These cameras are:
1. Too big to put in your pocket/purse/etc. so you don't carry them around as much as a point-n-shoot or a cell phone.
2. Too small to hold for a good posture to take pictures (one hand under the lens) yet the weight dictates some sort of two-hands operation.
3. Additionally, the "advanced" controls are buried deep under layers of menus, make them less usable than some of the more advanced point-n-shoot (like the Canon S100)
4. Lenses are not interchangeable with SLRs, so there is no upgrade path for those investments.
I would recommend you look at an entry-level DSLR (since the price points are close). Started out with the "green square" (automatic) modes, then learn to shoot in "P" (programmed) mode, adjusting ISO and compensations. Then move on to Av / Tv / M modes.
What you learn using a DLSR will be applicable to all cameras, and your investments in lenses won't be wasted.
Don't get me wrong, I think the mirror-less stuff is great, but the current crop of cameras leave too much out.
A great explanation, which made sense. But now I just have more questions. Like, "I will put a ball in one of these boxes, but I will not tell you which one I put it in. Now from your perspective, Neither the statement 'this box has the ball in it' nor 'this box does not have the ball in it' is true. You have no way of selecting which box I put the ball in." How is this any different?
What I am saying is, I don't see how there is any 'entanglement' there. It's just either in one diamond or the other. It's only our perception that doesn't know which one it is in.
I'd really love to get my head around this one day lol.
Actually, it works exactly as the entangled diamonds in this case. I don't know which box the ball is in, so you can bring one box to Mars, keeping one here on earth. Upon opening the box here (measure) and finds that it is empty, I can instantly conclude that the box on Mars has the ball.
All this assumes that the boxes remain "entangled". If someone changes the content of the travelling box en route to Mars, then all bets are off.
Since this is only a man-in-the-middle attack, it still requires an appropriate HDCP end point for each source, basically doubling the amount of gears they need to carry.
The research that goes into making the ISS a viable space station is important for the future. To ask if the ISS is worth $100 billion is like to ask if the wheel is worth 500 years of rolling things down hill, of if the splint axe is worth $x. If it were not for those things, we probably would not be having this discussion now.
We have the mean to fund such research. Therefore we should.
Anyone I've had in my car for the past several years, especially anyone who has an interest in being 'entertained' in a car, already had their own mobile internet and/or networkable device. Why would anyone want to splice an already-slow 3G connection between several people and/or devices?
Cuz, my map is red* and your is blue, duh!
----
* Disclaimer: customer might be cut off if usage exceed arbitrary threshold while in red coverage area.
Just nitpicking here, but how often do you explicitly declare or catch an ArrayIndexOutOfBoundException? It is, by definition, a RuntimeException, and only occurred when something *really bad* happened, e.g. indexing into an array using an invalid index. When it does occur, whatever that thread is doing should pretty much be thrown out, bug report filed, and programmers put back to work figuring out what really happened.
Just because a method declares that it might throw a particular exception doesn't mean you have to catch (or declare) exactly that. For example, there is nothing wrong with saying that your method throws an IOException when its dependencies throw a MalformedURLException. As the individual lines of code aggregate and become blocks and bigger blocks, the exception signature should become more generic.
A high-level block of code that deals with high-level IO should throw only IOExceptions. It might have to catch some other exceptions and convert it into IOExceptions, but the calling code doesn't have to know all that. All it need to know is that something went wrong, with the detailed information on the stack trace. Just enough to log the error, clean up the mess, and terminate.
Slashdot Mirror
I should have said data compatibility. Media has always been compatible.
... is huge! Now even a home user can have a tape robot for back up without worrying to be tied to a specific vendor. Well, maybe... but I can dream :)
http://www.dumbtionary.com/word/affort.shtml
This article on pharmacovigilance probably has what you're looking for.
Let's just add fancy graphics to this game and call it a day.
Until someone order a DCMA takedown on the site because it's used to store passwords for certain accounts.
That's my point of production cost vs. price. The article stated that currently it costs about $8000 to manufacture about 10kW worth of panels. The new process cuts it down to $4000. However, the current price is about $25000. If all the saving is passed on to the consumer, that would only cut it down to $21000. But you have to factor in capital investments, etc. so most likely you'd save maybe $2000 out of the $20000-$30000 for an installation. That's still 10%, but much less impressive than the 50% that the article seems to imply.
The price ($0.40/W) is the production cost for the PV panel. So, if you want to install, say, a 10kW panel on your roof, the solar panel itself would cost about $4000 to manufacture (as opposed to $8000 by other processes). How much it will cost you, however, still depends on market price, installation and infrastructure cost (batteries, inverters, switches, etc.)
:)
Now, a quick search shows that current panels sell for $250 for a 100W (or $25K for 10kW). And a whole system (< 10kW) is somewhere in the $20-$30K range. What that shows is most of the manufacturing cost of the panels is only a part (30%) of the whole. If all of the saving get forwarded to the consumer, you would see that the the cost might drop about $4K. So basically it'll take 16+ years instead of 20+ years to pay for itself.
After 25 years, you replace the panels and repeat the process, maybe at half the price
It is pretty obvious that electronic voting requires both anonymity (to remove fear of retributions) and accountability (to remove fraud).
About the only way to do that is to issue each person to have a pass-phrase coupled pair of electronic "vote cards" that is non-identifying. It would require the present of both cards and the pass-phrase to vote. If you lost one card, you can use the other (plus the pass phrase) to invalidate the lost card (and any recently casted votes.) If you lost both cards, you are SOL. No vote for you.
So, you just can't have a reliable electronic voting system.
... blow starting a car.
Now I wonder how many people will loiter outside bars, etc. rendering services to people who want to drive themselves hone.
With Windows XP going away, in a few years you might be looking for an old box to run your favorite program. In another few years you might be completely out of luck. Even further out, what if Microsoft went bankrupt (or bought by Apple, Google, RedHat, whoever) and their OS division is shelved?
:)
Projects like ReactOS, Wine, DOSBox, etc. allow you to have another possible path in that uncertain future. Your program might not work out-of-the-box, but you have the source to tinker with and try to get it to work.
That is probably the same reason for running Wine on Windows, which is probably better than running an old program within a virtual machine.
Soon enough, you will probably run all of your programs in a browser anyway. But I digress
So, do they embed impurities all along the fiber, or just at the very end, where it gets snipped off and polished before being attached?
How much of the signal is "processed" (i.e. lost) by the electronics if they are sprinkled all through the fiber?
Interesting stuff.
Father of the web? Wait 'till Al Gore hears about hears about this poser!
Web != internet
The biggest issue I have with the mirror less / micro four-third camera families is with ergonomics. These cameras are:
1. Too big to put in your pocket/purse/etc. so you don't carry them around as much as a point-n-shoot or a cell phone.
2. Too small to hold for a good posture to take pictures (one hand under the lens) yet the weight dictates some sort of two-hands operation.
3. Additionally, the "advanced" controls are buried deep under layers of menus, make them less usable than some of the more advanced point-n-shoot (like the Canon S100)
4. Lenses are not interchangeable with SLRs, so there is no upgrade path for those investments.
I would recommend you look at an entry-level DSLR (since the price points are close). Started out with the "green square" (automatic) modes, then learn to shoot in "P" (programmed) mode, adjusting ISO and compensations. Then move on to Av / Tv / M modes.
What you learn using a DLSR will be applicable to all cameras, and your investments in lenses won't be wasted.
Don't get me wrong, I think the mirror-less stuff is great, but the current crop of cameras leave too much out.
... and an assistant to hold the pet.
... is reason enough to get this bundle :) It's an awesome game.
http://positech.co.uk/cliffsblog/2011/12/14/humble-indie-bundle-4/
http://positech.co.uk/gratuitousspacebattles/index.html
A great explanation, which made sense. But now I just have more questions. Like, "I will put a ball in one of these boxes, but I will not tell you which one I put it in. Now from your perspective, Neither the statement 'this box has the ball in it' nor 'this box does not have the ball in it' is true. You have no way of selecting which box I put the ball in." How is this any different?
What I am saying is, I don't see how there is any 'entanglement' there. It's just either in one diamond or the other. It's only our perception that doesn't know which one it is in.
I'd really love to get my head around this one day lol.
Actually, it works exactly as the entangled diamonds in this case. I don't know which box the ball is in, so you can bring one box to Mars, keeping one here on earth. Upon opening the box here (measure) and finds that it is empty, I can instantly conclude that the box on Mars has the ball.
All this assumes that the boxes remain "entangled". If someone changes the content of the travelling box en route to Mars, then all bets are off.
Since this is only a man-in-the-middle attack, it still requires an appropriate HDCP end point for each source, basically doubling the amount of gears they need to carry.
It might be vast, but once you extract that heat and pump it into the atmosphere, wouldn't it cause a local cooling of the rocks?
How long would a drill site last without drilling more?
They actually lost offsite power: http://online.wsj.com/article/SB10001424053111903461304576526642400085456.html?mod=googlenews_wsj
The research that goes into making the ISS a viable space station is important for the future. To ask if the ISS is worth $100 billion is like to ask if the wheel is worth 500 years of rolling things down hill, of if the splint axe is worth $x. If it were not for those things, we probably would not be having this discussion now.
We have the mean to fund such research. Therefore we should.
Your microwave oven operates on the same frequency as Wifi, and 8:30-10:00pm seems like a likely time for it to be running.
:) if you turn it on and your wifi disconnect... bingo, time for a new, less-leaking microwave oven :)
It's also easy to test
Good luck!
Now find Atlantis.
Using LIDAR on Earth isn't going to help. Last time I saw, it flew to another planet.
Anyone I've had in my car for the past several years, especially anyone who has an interest in being 'entertained' in a car, already had their own mobile internet and/or networkable device. Why would anyone want to splice an already-slow 3G connection between several people and/or devices?
Cuz, my map is red* and your is blue, duh!
----
* Disclaimer: customer might be cut off if usage exceed arbitrary threshold while in red coverage area.
Just nitpicking here, but how often do you explicitly declare or catch an ArrayIndexOutOfBoundException? It is, by definition, a RuntimeException, and only occurred when something *really bad* happened, e.g. indexing into an array using an invalid index. When it does occur, whatever that thread is doing should pretty much be thrown out, bug report filed, and programmers put back to work figuring out what really happened.
Just because a method declares that it might throw a particular exception doesn't mean you have to catch (or declare) exactly that. For example, there is nothing wrong with saying that your method throws an IOException when its dependencies throw a MalformedURLException. As the individual lines of code aggregate and become blocks and bigger blocks, the exception signature should become more generic.
A high-level block of code that deals with high-level IO should throw only IOExceptions. It might have to catch some other exceptions and convert it into IOExceptions, but the calling code doesn't have to know all that. All it need to know is that something went wrong, with the detailed information on the stack trace. Just enough to log the error, clean up the mess, and terminate.