Skip to main content

Top Ten Science and Technology Predictions for 2010

I made a few long-term predictions in conversations over the past week about science in the next century. Focusing on only the next year is much more challenging. Also, I'll be proven wrong much more quickly.
  1. Mass market CPU/GPU hybrids are going to make netbooks and tablets very viable machines. HDMI outputs will make them powerful docked machined, capable of replacing a laptop realistically. Intel might have dropped the ball, but Nvidia's Tegra chips are going to prove this in the early half of 2010.

  2. Cheap DNA tests are going to be a noticeable social problem. We're going to see numerous news items this year about disgruntled parents trying to prove some fear with a few stolen strands of hair and a self-addressed envelop from a shady testing company. The legal and social implications aren't going to be pretty.

  3. At least one eBook reader will be released with color support in the US market. TMOS displays will appear in netbooks and phones. Our display technologies will continue to dive in cost and energy usage.

  4. Solar technology is going to hit a cost that will begin to make it a selling point for new housing development. There are likely to be new tax breaks for home's built or renovated with solar panels on the roof tops. This won't lessen the demand for the energy grid, but will slow its growth. The social idea of what a house is will begin to absorb energy production along with gutters, fake window shades, and central air.

  5. Bio-Fuel from algae will start to compete with soy and corn fuel in the sustainable fuels market. At least one company will start to sell commercial and possibly consumer targeted units for self-run fuel production. There are already such units available for breaking down biowaste, and a unit containing algae tanks is a sure attempt to be made.

  6. Google will begin public launches of plugin support for their major applications, starting with Google Spreadsheets' plug-in beta moving out of the sandbox and into Google Docs Labs. These plug-ins will run on AppEngine and be able to integrate with other products to extend and customize them in ways that aren't feasible for Google to do for the entire market. Don't expect to see a plug-in custom sorting your search results, but aside from Spreadsheets, I would expect Docs, Gmail, and possibly Picasa.

  7. The Google Nexus One phone will release and it will not be impressive. It will essentially be a shinier development phone mass-produced to give them better sample sizes for new experiments.

  8. The first commercial production trials of vat-meat will begin. People will be grossed out, but they won't ask if it's already being put in their hot-dogs or not.

  9. IPv6 will not be used much more than it was in 2009.

  10. No one will use public/private key signing, but they'll still complain about spam all the time.
You can see my list of other and upcoming 2010 predictions.

Comments

Popular posts from this blog

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally!

I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you
don't know a lot about software development, and probably don't even know a lot about computers in general.

Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year:

Python needs LÖVE.

LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build small Lua…

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 operate on. The only re…