Skip to main content

Power Pads, Cut My Loose Ends!

The idea has been floating around before, but finally seems to be coming into the light with efficiency and cost. The day will come soon when we can drop any of wireless devices onto a table and let them charge. When our desks will run power to everything sitting on them, without any connections or wires. Awesome.

They do say it could be many years before we get anything reaching wide support. The problem is that the devices need to support these new sources of power, and the devices won't support them until everyone has the new sources of power. You know how those great cyclic dependencies go. Now, we'll probably see them first in devices that are high end enough to warrant including stand alone power pads with them. I'll peg Apple's iPod as an early adopter.

However, I do have an idea to push these power pads more quickly: receives compatible with standard batteries. AA, AAA, and C are the most common batteries used today, so packing a receiver coil into the right shape unit would be just the ticket. That means any device taking a standard battery is automatically compatible with super convenient charging. The second step is for large deployments of non-standard batteries to migrate into receiver coils, allowing lots of existing devices like laptops and cellphones to suddenly gain the ability to charge wirelessly. As a bonus, putting the receiver coils in the batteries themselves allows you to toss extra batteries onto the surfaces for pre-charging.


Comments

Unknown said…
That's a great idea, assuming form factors get small enough, early enough in the adoption schedule. FWIW, there was an article in The Economist about this, so I guess it's "big news" now.

The worry I have is safety -- although this is inductive coupling, and thus very short-range, I'm not sure I'd like to store my hands and arms mere inches above it for the 10-12h/day I spend at my desk. At least not without understanding the health implications pretty well first.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro...