Skip to main content

How To Predict The Solid Web

Developers from both Opera and Mozilla have recently blogged about 3D rendering contexts for the canvas element, confirming my year-old predictions. Of course, the news is a bit saddened by the decision from Opera to support a new, non-GL-based API. I understand the desire for something more high level, but putting well known GL functions underneath is a perfectly acceptable idea. One side or a third party needs to provide a compatibility layer, or they need to decide on one of these APIs. I really hope OpenGL ES makes the win here. This also ties into the OpenGL APIs on Android, accessable through WebKit, so it only makes sense that Firefox, Opera, and all the WebKit-based browsers should standardize, before Redmond releases DirectX 1.0 Web Edition Premium.

For Users This Means...

We're going to see some fun web applications taking advantage of this, but there isn't a lot we'll see that we didn't have with Flash, for years now. I think some of the most interesting effects will come when we can use a canvas as a 3D texture and can render DOM elements into the canvas. When we reach this, we'll see lots of page effects, from folding elements to crumpled elements being deleted to rotating text and interface units.

We're going to see a lot of ugly abuse.

For Developers This Means...

Just one more thing to wait years before specialists are expected, and again you need to be a jack of all trades. Now you need to understand some code, a little database theory, CSS styling, artistic design, business layout, and 3D modeling and texturing. Have fun with it.

Comments

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 operate on

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