Oh look here are some SSD optimised file systems already. Incidentally they apply to these drives rather well.
Slashdot videos: Now with more Slashdot!
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).
It's still orders of magnitude, both in received power and amount of time the big transmitters have been around for.
And yes frequency plays a part too, but this article doesn't specify any frequency so even if some frequencies were bad, you can't say this one is bad.
Plus this one is induction not RF so it's different again.
Stick to the physics: https://yourlogicalfallacyis.c...
If you have a specific concern, tell us.
Otherwise I think the radio stations that have been pumping out megawatts for over a century kinda trump a couple of milliwatts over less than half a meter.
The difference is you know a launching rocket is definitely going to be at the launch pad.
If a landing rocket say misses by 10km whilst coming down, it is going to make a big mess.
A launching rocket could perhaps launch and then veer off back towards the ground but it is less likely to occur and can be killed a lot faster.
Landing on a barge is just a bit safer if something decides to go nuts.
More complicated, but if I lived in the neighbourhood of that Air Force launch pad, my insurance premiums might go up.
If the 'axe' is perfectly good, then why are you requesting fundamental changes to HTTP web apps and every web browser just to save your 8080 web server one additional hit?
Yep that sounds correct. That is the entire point of GET and POST being different.
GET retrieves data, never alters it. POST alters data, never retrieves it.
This is kinda HTTP 101. You might disagree, but then you'd be doing it wrong.
You are using a perfectly good axe as a door stop then whining that your teaspoon isn't cutting down trees properly.
Erm, but in that instance POSTing then doing a GET makes sense.
The POST creates the new user.
The GET retrieves the information for user 3813812.
How are those two things the same? That is exactly how it is supposed to be done.
If your server can't handle that 'additonal' load very well, then I've got a 486 upgrade I'll donate for free.
That is a feature. Auto speaker mute when you have a call.
User: "I bought this iPad from a white van"
Police: "So can you describe it?"
User: "Well it was white...and it looked somewhat like a van"
Sorry, Linux isn't a GUI. Which GUI do you dislike specifically?
Not sure how you say Linux is a clone of Windows when it is pretty well documented it is a clone of BSD, which Mac OS X is also a clone of.
Not if the items get sold before they are deactivated.
My Sony Z2 checks the GPS every now and then and doesn't even bother trying to use Wifi if I'm not actually physically near any of my known wifi points.
Stuff like that is quite sensible and practical. I equally get ridiculous battery life.
Isn't double buffering supposed to make it run at 60hz with a single frame doubled?
Yep single buffering would cause a progressive tear moving down the screen constantly.
Magnetic stripe + Signature = insecure.
Chip + Pin = A teensy little bit less insecure.
Over here in Australia, just a few months ago they removed signature as an option.
Every single credit card transaction must be PayWave or Chip + Pin.