Battery backed DRAM? As in, the kind that has to be refreshed 8000 times a second to prevent memory corruption? It's no damn wonder they can only get 16 hours of battery life.
What happened to good old SRAM? A real crosscoupled latch. The kind that has almost zero power consumption in steady state?
My old NES cartridges have lasted over 10 years on a single hearing aid battery. Granted, it was probably only 32 kbit of SRAM, but still.
While it is true that computer sales figures have to add up to 100%, market shares do not have to add up to 100%.
If each member of the computing public owns a pc that dual boots windows and linux, and a macintosh (heck, let's have it dual boot OSX and linux), then microsoft, apple, and linux each have 100% market share.
Why is that? Because an application developed for a particular platform (windows, linux, apple) could be purchased and used by any of the people in the computing market place, hence, 100% market share.
An Imperial gallon is 8 Imperial pints. An Imperial pint is 20 fluid ounces.
This is different than in American Standard units where a gallon is 8 pints, each being 16 fluid ounces.
Just to make things additionally confusing, the fluid ounce is also defined differently in Imperial (1 fluid ounce = 1 weight ounce) -vs- American Standard (1 fluid ounce = 1.04 weight ounce).
So, an Imperial gallon really does weigh (160/16 * 1) 10 pounds while an American gallon weighs (128/16 * 1.04) ~8.33.
An interesting departure here is in American Standard units.
A pint here is 16 ounces instead of 20 (though our ounce is slightly different too. A UK fluid ounce of water really weighs about 1 ounce. A US fluid ounce of water weighs about 1.04 ounces).
F=ma works splendidly well in imperial units. You just have to use the imperial unit of mass (slug) instead of the imperial unit of force (pound).
According to the google caclulator: 1 slug = 32.1740486 pounds
Well, that's true in Earth gravity (well, at the surface of the Earth (well, at the equator (well, at sea level))).
So really,
g = 32.some odd feet / sec / sec
g = 9.8some odd meters / sec/sec
which, if you were paying attention to this other article you'll notice a nice correlation.
Interestingly -- scales can only measure "weight", so a "pound" scale will always be correct. Scales that measure "mass" are only correctly calibrated for one gravitational environment.
This has nothing to do with the operating system, moreso to do with the applications.
I can write a program that requires read/write access to/etc/passwd, or/usr/bin for instance and guess what? It won't run without root access (or equivalent permission tinkering).
Most of these apps (for instance, Winamp) were designed for the single user windows 9x enviornment -- That is, these apps use the HKEY_LOCAL_MACHINE tree of the registry and require read/write in the %PROGRAMFILES%\AppPath directory. (Corresponding to the/etc and/usr/bin in unix world).
For proper operation under a REGULAR user account on an NT based machine, they should be using the HKEY_CURRENT_USER tree of the registry, and read/write in the %HOMEPATH% (Corresponding to.files in the home directory and ~/ in unix world).
Unfortunately, there's no easy way around this -- Windows 9X machines don't support the new semantics, and Windows NT machines require administrator access (or equivalent permission tinkering) to run apps deployed in Win9X style. On top of it all, Win3.1 apps drop INI files directly in the \WINDOWS directory! Truly hell for people developing an application that will properly deploy based on platform.
The only solution is to phase out old methodologies in favor of new ones -- by breaking reverse compatibility with deprecated (APIs, etc) -- and that's what Microsoft is doing with SP2.
RFID interrogators use a binary tree walking protocol to enumerate tags in the field. Get a tag that responds to every query, and you have effectively jammed RFID interrogation around your person.
This is just the first of many ideas; very simple but very effective. Just as many people are working on privacy solutions as are working on the rest of the devices.
It's a very lucrative market after all (privacy sector) because as as we all know: 1) FUD 2) ??? 3) profit!!!
Contrary to popular hysteria, RFID is not your enemy.
Slashdot Mirror
I'd like to point out that there are three common rectifier configurations consisting of:
half wave - 1 diode
full wave - 2 diodes (and a center tapped secondary winding)
bridge - 4 diodes
Battery backed DRAM? As in, the kind that has to be refreshed 8000 times a second to prevent memory corruption? It's no damn wonder they can only get 16 hours of battery life.
What happened to good old SRAM? A real crosscoupled latch. The kind that has almost zero power consumption in steady state?
My old NES cartridges have lasted over 10 years on a single hearing aid battery. Granted, it was probably only 32 kbit of SRAM, but still.
DOWN WITH TCP!
While it is true that computer sales figures have to add up to 100%, market shares do not have to add up to 100%.
If each member of the computing public owns a pc that dual boots windows and linux, and a macintosh (heck, let's have it dual boot OSX and linux), then microsoft, apple, and linux each have 100% market share.
Why is that? Because an application developed for a particular platform (windows, linux, apple) could be purchased and used by any of the people in the computing market place, hence, 100% market share.
Didn't you mean democrat?
No, julesh is actually right.
An Imperial gallon is 8 Imperial pints. An Imperial pint is 20 fluid ounces.
This is different than in American Standard units where a gallon is 8 pints, each being 16 fluid ounces.
Just to make things additionally confusing, the fluid ounce is also defined differently in Imperial (1 fluid ounce = 1 weight ounce) -vs- American Standard (1 fluid ounce = 1.04 weight ounce).
So, an Imperial gallon really does weigh (160/16 * 1) 10 pounds while an American gallon weighs (128/16 * 1.04) ~8.33.
An interesting departure here is in American Standard units.
A pint here is 16 ounces instead of 20 (though our ounce is slightly different too. A UK fluid ounce of water really weighs about 1 ounce. A US fluid ounce of water weighs about 1.04 ounces).
Thus, our gallons are 8*16 = 128 ounce weighing ~ 8.33 lb?
Okay, so not the easiest top of the head conversion factor... How did we end up this way?
A gallon of water is actually ~ 8 pounds. Or 8.345404 to be exact.
F=ma works splendidly well in imperial units. You just have to use the imperial unit of mass (slug) instead of the imperial unit of force (pound).
According to the google caclulator: 1 slug = 32.1740486 pounds
Well, that's true in Earth gravity (well, at the surface of the Earth (well, at the equator (well, at sea level))).
which, if you were paying attention to this other article you'll notice a nice correlation.
Interestingly -- scales can only measure "weight", so a "pound" scale will always be correct. Scales that measure "mass" are only correctly calibrated for one gravitational environment.
This has nothing to do with the operating system, moreso to do with the applications.
/etc/passwd, or /usr/bin for instance and guess what? It won't run without root access (or equivalent permission tinkering).
/etc and /usr/bin in unix world).
.files in the home directory and ~/ in unix world).
I can write a program that requires read/write access to
Most of these apps (for instance, Winamp) were designed for the single user windows 9x enviornment -- That is, these apps use the HKEY_LOCAL_MACHINE tree of the registry and require read/write in the %PROGRAMFILES%\AppPath
directory. (Corresponding to the
For proper operation under a REGULAR user account on an NT based machine, they should be using the HKEY_CURRENT_USER tree of the registry, and read/write in the %HOMEPATH% (Corresponding to
Unfortunately, there's no easy way around this -- Windows 9X machines don't support the new semantics, and Windows NT machines require administrator access (or equivalent permission tinkering) to run apps deployed in Win9X style. On top of it all, Win3.1 apps drop INI files directly in the \WINDOWS directory! Truly hell for people developing an application that will properly deploy based on platform.
The only solution is to phase out old methodologies in favor of new ones
-- by breaking reverse compatibility with deprecated (APIs, etc) -- and that's what Microsoft is doing with SP2.
Dude, it's five joules.
..... 0 degrees?
....... The guy would heat up 24 K/sec .... he'd evaporate in a matter of seconds!!
The specific heat of water is 4.18 J / g * K.
Assuming one 100 Kg guy absorbed ALL of the energy, he'd heat up all of
That wouldn't tan me very much...
Now, if they could sustain 10 MW countinuously
People love to whine about rfid privacy, consider:
l o-TheBlockerTag.pdf
http://theory.lcs.mit.edu/~rivest/JuelsRivestSzyd
RFID interrogators use a binary tree walking protocol to enumerate tags in the field. Get a tag that responds to every query, and you have effectively jammed RFID interrogation around your person.
This is just the first of many ideas; very simple but very effective. Just as many people are working on privacy solutions as are working on the rest of the devices.
It's a very lucrative market after all (privacy sector) because as as we all know:
1) FUD
2) ???
3) profit!!!
Contrary to popular hysteria, RFID is not your enemy.