Chris Bateman

The Increasing Ubiquity of JavaScript: Part 2

Last year I wrote about the increasing ubiquity of JavaScript. It was about the increasing use of JS for tasks previously done natively. I also wondered what would happen when native developers started spending more time in JS. This is just a couple quick follow-ups.

Stavros is a programmer from Greece. He does low-level assembly coding, graphics programming, language and compiler design, UI development, artificial intelligence, and CPU/GPU architecture. He recently decided to learn JavaScript, in order to get into web development.

When I tried to think of a project suitable for learning JavaScript, a terrain flyover demo came to mind.
Take a moment to look at what he came up with. Now take a moment to think about your first JavaScript project.

A new version of the game SimCity was recently released. Its UI was done entirely in JS, running on Webkit.

Steven Wittens explains the draw of using HTML in native games:

I wonder for example how many hours of dev time the game industry has spent reinventing the wheel for fonts, menus, option screens, etc. To be fair, they often do so with amazing production value. But guess what: you now have CSS 3D, and soon you’ll have CSS shaders. You don’t need custom in-house tools when your designers can just use Chrome’s Inspector and get the exact same result.
Tell me what you think: @batemanchris