That doesn't match my interpretation of the numbers.
I expect we'll see a big downswing in the next few weeks, and my gut is telling me the bottom is at $15/BTC.
In fairness, at least half the time that gut feeling is gas.
I fully expect that we'll have about 16 months of "normal" trading after this crash, then it will spike again, but I'm only feeling that the next spike will go to around $325.
No. If you run all of the downloads in parallel then one of them still finishes first and can be used while the others finish off.
Great, assuming that I don't care which one I get first. Perhaps I started downloading a particular selection first, because I want it before the others. This also assumes that the storage isn't hindered by fragmentation (with modern systems, it probably isn't hindered much), or can handle such fragmentation in a good way.
Also, when the available bandwidth per-stream is lower than the available bandwidth per-link it is quicker to run the downloads in parallel.
While technically correct, this case hasn't been my usual experience.
Lastly, when the total bandwidth across all the streams is still less than the link (which is frequently true) then the sequential time of each is unaffected by running them in parallel, but the total time is greatly reduced.
It sounds like parallelization vs serialization of downloads should be a user selectable preference..
When connected to WiFi or 3G/LTE, there's no reason why multiple simultaneous downloads shouldn't be used
If bandwidth is finite, serializing downloads means one finishes first, and can be used while the others download.
You're right on the RAM usage, however - particularly with eBook readers. It's reasonable to keep them in-RAM, or at least keep enough in-RAM so you can turn a few pages forward or back without loading.
And shouldn't drone pilots from and within the USA be just as much a target for targeted killing by the "other side" even while they are located in the USA geographical boundaries?
Yes.
Just because the weapons have a longer reach, that doesn't mean the person at the controls isn't a valid target.
No, but Kansas might go to hell if he couldn't leave.
Not trolling; the few times the POTUS has been here in town, traffic gets messed up all day. It's obnoxious. About 20 minutes after Air Force One is wheels-up, things are back to normal, and people can get from place to place.
Your strategy reminds me of a vendor I had to work with. I dislike that particular vendor only for their draconian software licensing enforcement*.
Supporting an authorization scheme like that is reasonable if you're a big business company and your customers are also big business.
For everyone else, it's an undue hassle.
Frankly, for a $5 application, tying it that heavily to the hardware will cost more than the money you're making.
*I don't object to licensed software; but in this case, the software had no utility or value unless it was being used to communicate with a piece of their hardware. Managing the licensing on the software just so the engineers could talk to their hardware was an unneeded hassle, and we ended up switching to another vendor's hardware (and software) because their interface software wasn't pathologically broken by licensing.
just designing something that lasts longer than its mission goals is, when taken alone, an epic failure when you're talking about thousands of dollars per kilo to launch.
I disagree, for the simple reason that if we can spend slightly more incrementally and increase the service life significantly, we can keep getting data without having to design and launch a brand new system (for many more kilos of launch cost).
If we can spend one extra kilo and get 10 extra years of service, that's probably a good tradeoff. If we spend one extra kilo and get 100 extra years, that's a great tradeoff.
Because if they want to move the thing around (quickly) and have it be somewhat immune to wind, a blimp isn't going to be able to keep up. Blimps are slow and get caught by the breeze.
Slashdot Mirror
Totally useful if you're more than say 50 miles from home.
If you're less than 50 miles from home, they know where you are anyway, and can triangulate your position.
Which autopatch are you suggesting that can answer a ringing line?
Most of the cash prepaid phones still demand a name and address to activate. (YMMV... who are you using for burn phones these days?)
Better put the phone into your pocket faraday cage...
Great. Another ad for Aluma-Wallet. Didn't realize they had a giant one now, big enough to fit a common smartphone.
They're solid states drives. No vacuum tubes used in the assembly.
I don't know, let me think about it after this round of Fruit Ninja.
Magicking $1 trillion out of thin air would make the US government very happy.
My understanding is that the US Government isn't authorized to generate revenue that way.
Yeah, but your Special Agro-Cheques are all expired.
That doesn't match my interpretation of the numbers.
I expect we'll see a big downswing in the next few weeks, and my gut is telling me the bottom is at $15/BTC.
In fairness, at least half the time that gut feeling is gas.
I fully expect that we'll have about 16 months of "normal" trading after this crash, then it will spike again, but I'm only feeling that the next spike will go to around $325.
Yes, please sell.
Collapse this round of the bubble, so I can get in at $17 for the next round.
No. If you run all of the downloads in parallel then one of them still finishes first and can be used while the others finish off.
Great, assuming that I don't care which one I get first. Perhaps I started downloading a particular selection first, because I want it before the others. This also assumes that the storage isn't hindered by fragmentation (with modern systems, it probably isn't hindered much), or can handle such fragmentation in a good way.
Also, when the available bandwidth per-stream is lower than the available bandwidth per-link it is quicker to run the downloads in parallel.
While technically correct, this case hasn't been my usual experience.
Lastly, when the total bandwidth across all the streams is still less than the link (which is frequently true) then the sequential time of each is unaffected by running them in parallel, but the total time is greatly reduced.
It sounds like parallelization vs serialization of downloads should be a user selectable preference..
It's a less noticeable impact, but FLASH is still slower than RAM.
When connected to WiFi or 3G/LTE, there's no reason why multiple simultaneous downloads shouldn't be used
If bandwidth is finite, serializing downloads means one finishes first, and can be used while the others download.
You're right on the RAM usage, however - particularly with eBook readers. It's reasonable to keep them in-RAM, or at least keep enough in-RAM so you can turn a few pages forward or back without loading.
managed to gain complete control of it
Aiming the camera under remote control via software is a pretty good trick. Ordinarily, you need to mount it on a pan-tilt device.
Removing the lens cap from software is another good trick. Powering the thing on remotely with batteries removed is amazing.
Yes, this is pedantic, but I'm guessing they don't have complete control of the camera. They may have control of the camera software.
Cheap untraceable guns means little, if the stores are out of bullets.
Perhaps not, but we might attack their undersea communications cables in international waters, unplugging the attackers.
And shouldn't drone pilots from and within the USA be just as much a target for targeted killing by the "other side" even while they are located in the USA geographical boundaries?
Yes.
Just because the weapons have a longer reach, that doesn't mean the person at the controls isn't a valid target.
A nation should be able to retaliate against attack.
It would be morally wrong to not try a hacking counterattack first, however.
No, but Kansas might go to hell if he couldn't leave.
Not trolling; the few times the POTUS has been here in town, traffic gets messed up all day. It's obnoxious. About 20 minutes after Air Force One is wheels-up, things are back to normal, and people can get from place to place.
Your strategy reminds me of a vendor I had to work with. I dislike that particular vendor only for their draconian software licensing enforcement*.
Supporting an authorization scheme like that is reasonable if you're a big business company and your customers are also big business.
For everyone else, it's an undue hassle.
Frankly, for a $5 application, tying it that heavily to the hardware will cost more than the money you're making.
*I don't object to licensed software; but in this case, the software had no utility or value unless it was being used to communicate with a piece of their hardware. Managing the licensing on the software just so the engineers could talk to their hardware was an unneeded hassle, and we ended up switching to another vendor's hardware (and software) because their interface software wasn't pathologically broken by licensing.
Chuck Norris always has been, and always will be, "in his prime".
just designing something that lasts longer than its mission goals is, when taken alone, an epic failure when you're talking about thousands of dollars per kilo to launch.
I disagree, for the simple reason that if we can spend slightly more incrementally and increase the service life significantly, we can keep getting data without having to design and launch a brand new system (for many more kilos of launch cost).
If we can spend one extra kilo and get 10 extra years of service, that's probably a good tradeoff. If we spend one extra kilo and get 100 extra years, that's a great tradeoff.
Won't someone please think of the scientists!
No! No! Not in that way!
I'm sure that really isn't a problem once you've seen a photo of the department team.
The reference.
Because if they want to move the thing around (quickly) and have it be somewhat immune to wind, a blimp isn't going to be able to keep up. Blimps are slow and get caught by the breeze.
Woosh..