The picture depicts one car though. That would likely imply that you could send multiples though the tube, kind of like rail cars are sent along the rails.
The big thing is that these will travel much faster.
Look at the volume of the car, it is tiny compared to rail. Faster isn't a big help since we already have efficient air for that. Heck, we still use barges for cargo. Plus, the whole evacuated tube would play hell on cargo loading because of the added requirements. Speed buys very little given cargo is fine with traveling all night.
Keeping track and sticking buttons all over the place is going to be an "early adopter" feature. Once we get to an overwhelming number of "buttons" it will make sense just to put up a couple cameras similar to the Microsoft Kinect and use hot zone + gestures to do the same thing. RFID in boxed products might help out but the buttons will end up being a mess right quick.
It is cheaper to put microphone and ask for food, similar to regular shop: "Hey, Amazon", "Order, please", "Bottle of milk and bread", "Bottle of milk «Foo» $2,50. Bread «Bar» $1,75. Total: $4,25. Confirm?", "Yes", "Order accepted, wait for delivery.". Something like Siri, but activated by push of hardware button on the fridge.
Yep. But it's a closed-source always-on cloud-connected microphone that lives in the middle of your house, which creeps the hell out of a lot of people (including myself and most of my housemates).
Interestingly enough, when I signed up for Amazon Fresh, I got a version of the Dash that is multipurpose. Instead of having buttons everywhere, mine has a barcode scanner, and voice recognition. When I am out of eggs, I just pick it up, push the "Mic" button, say "Eggs," and it appears on my "Dash" list when I log in to Amazon Fresh.
By relying on closed software on the Drives controller chips wouldn't it just get more complicated? With the price of RAM being as cheap as it is, why not just build a series of systems with 100GB+ of RAM and cache away?
Relying on a drive controller might seem the right way to go but especially for corporate installations I would believe it would be beneficial to have the fine grained control a dedicated server could provide.
Because systems, including servers, don't expose an abstraction of being permanent (always-on) storage that never gets suddenly lost (rebooted, loses power) for any reason at any time. How could you run a laptop with a server inside that cached 100GB+ of RAM? You would have to wait for it to load from RAM. Not so with the device I outline: if it has 48 hours of trickle charge (my calculations could be wrong but apparently it just takes mere milliwatts to refresh a DIMM), then as long as it has received power in the last 48 hours it would be instant-on. Everything you do is instant, EVEN IF it's written against software that writes to permanent storage.
only if you think having every disk access occur at ram speed rather than SSD speed makes no difference. CPU's and RAM are so fast, I think often in starting an application or the like, disk access really is the limiting factor. I suppose you can disagree. things like compilation could easily end up twice or five times as fast in my estimation. know anyone with a compilation in their workflow?
I should have said "C: drive"/"HDA1" but wrote boot media so I could save having to think about my phrasing. I meant that's where you would install anything that is primary to your workflow and might read and write lots of files, because that's how it was programmed, git, your ide, compiler, test suites, database, webserver and log files, or whatever programs you create and handle your workspace with, whatever that may be (photoshop, design software, etc).
the point is, things you would never risk not having on permanent storage, and which are written with the expectation that they will be. if it's ironclad (six/seven sigma, and backed up to real permanent storage behind the scenes in case worse comes to worst), you wouldn't have to give up this abstraction. it would still be a hard drive and not, you know, the current contents of your ram since you booted.
I just can't seem to figure out where you are coming from on this. My first question is, why would you plug a device with transfer rates in the 20-40GB/s range into a SATA3(6Gpbs) port?
Next is although we can wax poetically on what exactly is the best case for every ones use cases how are you going to guarantee that the micro controller will work the way you want it to?
Databases with properly configured indexes will retain the important data in RAM with out further modifications, and again how would you ensure that the records you feel should be cached are cached since the small micro controller would barely have the resources to analyze the data stream to begin with.
Lastly if you do care about data retention during power outages and sags then you would likely want an APC/backup battery. Even though the data stored in the SSD/RAM hybrid might have enough backup power to flush to disk how about the data that is currently in RAM waiting to be flushed as well?
I still don't understand. If you have tons of RAM, your OS uses it for cache, so disk access is at RAM speed. I only reboot my computer a few times a year, so if I had 256GB of RAM in my computer everything I use at least once a month would be in cache.
I doubt very much that this is the case. Your OS can't possibly report to, say, your database, that something is written, if in fact it is still being written. Likewise if your compiler produces a bunch of object files before linking them, your OS won't just stick them in RAM and say "well, there's your file, it's written" while not actually being written. I just don't think it works that way!
If it did, SSD's wouldn't be so much faster than spinning-platter HDD's...
A buffer cache in write-back mode would do this, but DBMSs are usually very strict when it comes to waiting for data to hit long-term storage. Most of the implementations access the disk directly, bypassing such mechanisms in the process.
SSDs are still faster for non-cached reads, which are significant, since most people don't have as much RAM as they have of permanent storage.
By the way, what you're proposing in terms of software has been available for a long time; multiple distros (including Ubuntu) can/could be booted completely to RAM, using tmpfs as the filesystem. For example:
At the boot prompt, type "knoppix toram". Knoppix will load the contents of the CD into ram and run from there. After boot up, the CD can be removed and the cd drive will be available for other uses. Because this will take up a lot of ram, it is recommended for those with at least 1 GB of ram.
It's definitively faster, I just don't have the necessary RAM to fit all my system in there.
Not only that, at the first power loss you would lose all your data. I wouldn't boot anything critical straight to RAM! It's just not the kind of guarantees we're used to.
If it were all in a sealed package that 'guarantees' the RAM will never power down, at a very low firmware level, that is a different matter.
If the malware came from the Police computers then wouldn't that likely taint all the data supplied, to well everyone? Every defendant for at least the last year will be taking a shot at this and why not?
There's really only 4 possibilities, and they're all significant.
1) PD is responsible, and intentionally infecting defense attorneys with malware. Major obstruction of justice.
2) PD is responsible, and has been hacked. At a minimum, all their computer evidence is tainted; who knows if someone has been using their access for ill as well. Access to police DBs is useful for all sorts of nefarious purposes.
3) Defense attorney has faked the whole thing. Noteworthy in its own right; defense attorneys are pretty used to losing as a matter of necessity so for one to go on some kind of intentional crusade against the local PD, especially in such a public and falsifiable way... No judge will sign off on criminal sanctions here without a thorough investigation, so this is extremely unlikely barring a psychotic break (which does happen now again, it's a high-stress job).
4) Defense attorney has been hacked. Who hacked him? Have any of his clients been affected? Is someone, perhaps a technically sophisticated someone, targeting defense attorneys?
That fourth one is the killer. Regardless of its truth or falsehood, it gives everyone an out because none of the interesting consequences of the first three have to happen.
Perhaps the proper move would have been to surveil the malware without revealing that you know of it. Could prove/falsify #4, or implicate PD conclusively if #1.
When you are dealing with a city of millions does it really seem right to fish one wire at a time? That means terminating the wire at the home too. With multiple ISP's how many of them would need access to the "Main St" section at a time? The cost of booking a time, sending a worker out to fish and terminate possibly kilometers of wire per customer as each customer signs up would be a logistical nightmare. Then what happens when the customer leaves you for the other guy? Never mind the cost differential of running one wire vs bundle of wire.
Even though their TOS might state that, it's extremely poor PR to go after the end user rather than the distributor. Most people won't even know that they have a counterfeit chip. Even though it may be well within their rights the customers will eventually find out what they have done and bear a grudge.
Don't be so obtuse. A law is a written order, adding the remainder is just an inflammatory accusation that undermines the public at large.
You may believe that the public or those governed by which ever particular law you select are too scared or ignorant and have the law imposed on them from outside interests but the greater numbers always win in the end. A particular rule of law may be arduous today and for many more consecutive days but one day the rule will change.
This is evident throughout history and will continue to be.
> A law is a written order, adding the remainder is just an inflammatory accusation that undermines the public at large.
Undermines the public how?
> A particular rule of law may be arduous today
"Rule of law" is a misnomer. It's actually rule by those who decide what the laws are. That would be the "elected representatives", ie. politicians of course.
In other words, politicians are our rulers because they make the rules that are ultimately enforced at gunpoint, if you don't feel like obeying at first.
But a law is just text somewhere. But even if the text contains a decree on what everyone must or must not do, that alone does not change people's behaviour one bit.
For example, if I write down on a piece of paper that you have to give 30% of your income to me, will you do it? OK, what if I threaten you with imprisonment if you don't?
You seem to be overlooking the point. Would it be morally permissible for me to scribble down arbitrary rules and enforce them on you if I had an army with which to ensure your compliance?
Laws are just arbitrary rules decided on by a small group of people, much like they were with Kings and their inner circles. Laws are enforced in much the same way too - there's no practical difference between getting assaulted by the King's Guard and getting assaulted by men in blue costumes.
True but wouldn't the landing pages of most of these services be able to document the OS, browser, resolution, type of device(tablet vs laptop and IOS vs android) and likely a lot of other stuff.
I can narrow down a huge list to a very short list using above information along with the probes being sent out co-related to the signal strength. Timing of each probe can also be leveraged in uniquely identifying,most probes are sent in interval from each device. Those probes that come in equal intervals are likely from the same source, leveraged against signal strength you can likely identify a small crowd. To take it even further you can calculate the signal as absorbed through the store to signal congestion and possibly other metrics.
Hence the "using this tracking method" caveat. Now you have to do something much more complicated just to get less specific data. And it's a cat and mouse game: You put up a useless landing page, device makers set their browsers to require TLS for any page previously found to support it, preventing you from redirecting requests to the majority of popular sites. Or they could just detect the ARP misuse that makes captive portals work and patch that particular vulnerability, because screw captive portals entirely.
The big thing is that these will travel much faster.