Atari announced that tomorrow, a free iOS app named Circus Atari" will be available in the App Store. The original Circus Atari for the Atari 2600 was compelling game that blended physics and Breakout.  It was one of the best 2600 games of all time.

The new Circus Atari looks different, but still like a cool little game.  We are very happy to see Atari continue to mine their back cataloge for gaming goodness.

One day, back in 1978 my dad came home with this:

A Radio Shack, TV Scoreboard console.   We had been begging my dad to let us play the Atari 2600 console in the TV department at Fedmart on every visit, so he knew we liked video games.  However my dad, a notorious cheapskate, was not about to plunk down $169.99 on anything.  $19.99 price-point of the TV Scoreboard was more his speed.  However, even $19.99 was probably too much.  i'm sure this came from the dirt-cheap bargain bin from Radio Shack.

At first, my 8 year old twin brother brother and I were really excited.    The idea of having a video game of my own to play was enough to rocket me out of bed in the morning and into the living room to try it out.

Of course, this taught me my first lesson about video games.  If no one else was awake, there was no one to play with.   The TV Scoreboard had a "Squash" option that let a single player hit a ball against the wall, but I never found that game very interesting.  I wanted to play "pong", and if no one was around, no dice.

When my brother was awake, and we actually played the unit, the second major issue reared its' head: sound.  Like most dedicated "pong" consoles, the limited sound of the TV Scoreboard   came from the unit itself, not from the TV.  This made the already lo-fi beeps and boops even more annoying than I thought possible.  We very quickly learned to shut the sound off, and play in silence.   While the "pong" style game play of the unit was solid, nuances (like bad sound) ruined the experience.

The third thing I learned from the TV scoreboard was that "ping pong" games were not really all that much fun.  Maybe six years earlier, when Pong first arrived, the game was thrilling, but in 1978, with Space Invaders filling the local arcades, the "ping pong" game play of the "TV Score-bored" (as it came to be known) was just not compelling enough.

Those three lessons: the need for  compelling single player game play, the importance of nuances in games, and the need for evolving game play, have colored the design for the Pong game we are making for the Atari Pong Developer Challenge.  I hope we can do those hard learned rules some justice with our entry.

By the way, the "TV Score-bored" stopped displaying video after a few weeks, but since the sound came out of the unit and not the TV,  I could still "play" it by starting a game and listening for the sounds and moving the paddles.  If I managed to "hit" a ball,a distinctive beep would sound, and I felt totally victorious for few seconds.  On the other hand, my dad felt "taken" by the "cheap-o" device after it failed do quickly.   It would be several years before another video game system entered our house.

More than two years ago we started taking a close look at the HTML5.  To us, the  HTML5 features like <canvas>, <audio>, and <video> were the most compelling part of the HTML5 spec because they were poised to be a true replacements for Flash.   Flash had been our tool of choice for over a decade because it worked....most of the time.   For the corporate web, 'entertainment, media, gaming web sites, it was second to none.  Sure, it had issues: security flaws, proprietary API walls, performance hang-ups, etc. but it was also a simple platform.  Write your AS3, marry it to assets created by designers in .fla, export .swf, done.    A simple process for a powerful technology.

All was right with the world.

Up until last November, it is our firm belief that most Flash Web developers were holding out for Flash support on mobile iOS browsers.     "Apple will come around" we thought, "Flash will run in the iPad 3 and the iPhone 5" we fantasized.  Not because we thought Flash was perfect, or because we did not like the idea of HTML5, but because, for more than decade we had tasted what a real "standard" might be like.    We've heard about "web standards" for years, and they are a beautiful,  poetic, amazing concept that never quite came to fruition because OS, browser and platform companies had their own ideas on what was standard and what was not.  However, with Flash, we truly had ate from the "write once, run nearly everywhere" table we had been hearing about for so many years.

Then last October, Abobe gave up the mobile web, and all hell broke loose.

Web standard guys applauded it, and Flash guys continued the hand wringing operations they started back in 2010 when Apple announced the iPad would not have Flash support.    Not too long after, It seemed, all at once, the rush was on for HTML5.   Flash developers knew they needed to move on, and web standards people had their last stumbling block removed.  The plug-in-less HTML Renaissance had begun.

But then something weird happened.  Even though, when we said the phrase  "HTML5" we were talking about <canvas>,<audio><video>, local storage, geolocation, and new mark-up standards,   we noticed that when customers asked for HTML5, they had no idea what was part of the actual HTML5 spec.  When we talked to other game developers about HTML5, some had never used any specific HTML5 features.   They were using traditional web technologies like HTML, JavaScript, DOM, CSS.   In fact, in many cases the only true "HTML5" they were incorporating was the <audio> tag, and most of the time, it wasn't doing what they wanted it to do.   While features like the HTML5 Canvas are growing in use as mobile browsers get more powerful, it turned out that HTML5 meant many things  to many developers, and that did not always include the actual features of HTML5 once outlined by the W3C.

So then what *is* HTML5?  The W3C HTML5 FAQ  says this about HTML5:

HTML5 is an open platform developed under royalty free licensing terms. People use the term HTML5 in two ways:

• to refer to a set of technologies that together form the future Open Web Platform. These technologies includeHTML5 specification, CSS3, SVG, MathML, Geolocation, XmlHttpRequest, Context 2D, Web Fonts (WOFF) and others. The boundary of this set of technologies is informal and changes over time.
• to refer to the HTML5 specification, which is, of course, also part of the Open Web Platform.

What we have learned through conversations and project work in the past few months is that, to the common person who does not follow this closely, (or more likely, the common customer who needs something done right away) it's all HTML5, and therefore they are really referring to the "Open Web Platform".  In this way, HTML5 is just as much and "idea" as it  is a strict specification, and that "idea" of the "Open Web Platform"  has caught-on like wildfire, even if the borders that define what is actually included in "HTML5"  have never been fuzzier.  However, the one thing we do know is that at the kickoff party for the "Open Web Platform", the one technology that was definitely left of the invite list was Adobe Flash.

But who was invited to this "Open Web Platform Party?"  Well of course  HTML5,  CSS and DOM plus  SVG, Web Workers, Web Storage, Geolocation,  and Web Sockets.  Then experimental stuff like the  Web Audio API,  and Media Capture...and that just scratches the surface at the W3C.   We also need to add  JavaScript and WebGL, WebKit, which are run by other organizations but are just as important.  Then we have  Modernizr  and the king of JavaScript APIs, JQuery.  JQuery is so popular, in fact, there appear to be entire religions formed around it.  JQuery adds  JQuery UI and  JQuery Mobile . In fact, Some people have told us that we will never need any thing  else, if we just decide use the JQuery suite.    Really?  That would leave out  all these other technologies we keep hearing about like  MooTools, ExtJS, Sencha Touch, Ripple,  JQMobi, Jo JoshFire, Inuit,  LungoJS  and the Dojo toolkit.  Those seem pretty cool too and they all claim to solve the same  HTML5 cross-platform issues.   But then, so do  DOM/CSS tools and templates like   HTML5Boilerplate,  Initializr, Bootstrap, Crafty.DOM, LESS, 960, Blueprint, 52 Framework, Gravity,  Gridless, Skeleton, G5 and many others.    At the same time, if you want to make,  "HTML5 games" there are a whole different set of technologies to consider  like Construct 2, CreateJS (now with more Adobe), Game Maker, KineticJS, Processing.js, ImpactJS, LimeJS, Jaws, Box2SJS, CasualJS,  Cocos2D, EntityJS, GameJS, GMP, Isogenic, PlayN, PropulsionJS, Mibbu, Sprite.js and many more plus WebGL libraries like SpiderGL, GLGE, Copperlicht andSceneJS.   Then there are JavaScript media libraries like VideoJS, MediaElementJS,  Kaltura HTML5 Media Library, Jukebox,  Buzz audio library, and Popcorn.js,   Plus other tools like RGraph for graphing,  Mashi for timeline animation, BakerFramework for ebooks  or  Pixtastic for real-time image filters. And we can't forget the HTML5 app hosting and development platforms like AppMobi, Spaceport.io, FunSockets, Turbulenz and Pixie Engine or the fact that we can package up all this stuff and make them into mobile apps with  phoneGap,  or Appcelerator, or Apache Cordova.   And if you want to take your JavaScript all the way to the server-side, well then node.js  and Kinvey are just for you!  A lot of these technologies claim to be "only" way to go, so which do we choose?

And then we need to mention the platforms and devices.  Just a few years ago, we all wrote apps for Firefox, I.E. and maybe Safari, but only if you were a glutton for punishment.     Now we have to consider multiple versions of Internet Explorer, Chrome, Safari, Mobile Safari, Firefox, Opera,Silk,  the 30 or so combinations of iOS devices and operating systems, and 1000's of Android device and OS combinations.   To further complicate matters the general consensus, at least among customers,  is  that web apps made with  "HTML5 open Web Platform"   should run perfectly across all of them.

In the past couple weeks, an angsty zeitgeist has appeared to form like a cloud around the "HTML5 Open Web Platform".    It's the feeling of technology burnout for developers, while at the same time they try to manage the expectations of customers who are clamoring for a one-size-fits-all solution to their web development needs. Our own cartoon on the subject was a minor hit for us:

And the feeling might be spreading. Just a couple days ago, the hilarious parody technology site HTML9ResponsiveBoilerStrapJS  appears to captures the feeling of HTML5 technology burnout perfectly and scored a sizable hit via twitter:

"H9RBS.js (v0.0001) is a flexible, dependency-free, lightweight, device-agnostic, modular, baked-in, component framework MVC library shoelacestrap to help you kickstart your responsive CSS-based app architecture backbone kitchensink tweetybirds."

To us, the buzzwords are flying left and right, and everyone seems to be trying to solve  similar problems by creating multiple new technologies and tools.    On one side, this is a very cool development.  It's a evolution and revolution, and we are happy to be part of this mini-tech bubble that has moved-in to fill the gulf left by Adobe when they abandoned the mobile web. On the other had,  the sheer amount of "new" around HTML5, be it ways to describe code, templates, technologies and platforms is dizzyingly overwhelming.  The situation is confusing at best, and confounding at the worst.   Furthermore, most " tech bubbles" are inevitably followed by a shake-out where dozens of also-rans fall by the way side (Remember when Flash put DHTML, Silverlight, Applets, JavaFX, VRML, Realplayer and Shockwave, off the map?). For developers, this means being very careful to choose technologies that we believe will be around for the long-haul, or we run the risk of investing our limited time and resources into something we will never use again.

All we really know right now, is that when people ask for "HTML5", they don't always have a specific technology in mind and they probably have not read the W3C spec of what is actually in "HTML5".   They might know a bit about things they perceive to be HTML5 like  CSS3 or Webkit,  Canvas or <video>, but that's not really important.  What's important is the translation of the question.  When they ask for HTML5, they are probably saying they want a single web site that runs on all devices, mobile or others and that then translates into:

"Not Flash"

And to developers who were once comfortable using Flash as a cross platform silver bullet, that could mean wading through a whole lot of specs, tools, APIs of the "Open Web Platform" before the proper solution is found for the project.

So when you call us now and ask for a game, site, app, etc. in HTML5, and there is slight pause in the conversation before we give you an answer, it's not because we are bored,  disinterested or distracted, it's because we have a few extra things to consider these days before we can  formulate a proper response.   If you give us a few minutes to catch our breath, we promise, the end result will be awesome. We appreciate your patience.

Here is a video we created to help inspire our team while we work on our entry for the semi-final round of the Atari Pong Developer Challenge.   We used a classic Atari color cycling Fuji symbol (of our own design) with images of some of Atari's early Pong coin operated games.  The music is a quick track made with Sony Acid.

By Steve Fulton

A few weeks ago I wrote an article about my efforts as complete "non-artist" to create funny, classic video game inspired photo-shopped images for Cracked.com "Photoplasty" weekly contests.   The gist of the story was that, even though cracked.com never features any of my images, the effort on my part to push my myself to "be creative" was still rewarding.  Afterwards,I quit making the images because it was taking too much of my time.

Well, last week when I saw they had posted a contest theme named "Video Game Plot Twists That Would Have Blown Your Mind" ,I decided to try again using a  "lessons learned" approach.  So instead of making images that feature games that are my favorites, I decided to instead, use games that Cracked.com seems to fall back upon when choosing images.  I threw out my standbys of Pitfall!, Asteroids, and  Food Fight, etc., I decided to pick from games that I see often used in these contests like Space Invaders, Frogger, Paperboy, Metroid, and Super Mario.  At the same time, I decided to create an animated .gif instead of still image, because those types of images seem to get chosen more often.

Anyway, of the three entries I created, Cracked.com chose my Space Invaders image as #16 for the week.   The image was inspired by the pilot episode of the The Twilight Zone.  To be honest, I don't even think the image is that funny.  I think they chose it because it did not look like any of the others.

So what did I learn form this?  I suppose the lesson is "know your audience", or "keep trying"  or something like that.   Or maybe there is no lesson to be learned at all.  I'm still trying to decide.

By Steve Fulton

In 1994, about a week after I moved out of my parents house and into an apartment with my brother, our cable TV was installed.   For the first time in my entire life, I could watch MTV any time I wanted.    When I turned on MTV for the first time, this is the video that was playing:

I was 24 years old, and all of sudden I felt something I had never felt before: Nostalgia.   Seeing this landmark Sabotage video by the Beastie Boys did what it was supposed to do: it  made me recall all the cheesy cop shows from the 70's we watched because there was nothing else on TV. Shows like like Starsky And Hutch, The Steets Of San Francisco, Hawaii Five-0 and SWAT.    The Beastie Boys made a song that was sounded completely new and modern, but the video took inspiration from the past: looking back while looking forward.  The song still sounds as good and relevant today as it did almost 20 years ago, and the video still works amazingly well.

As I watched the video that day, I recall my thoughts turned to one of the great, amazing things that came from the 70's that made me forget all those terrible  TV shows: the Atari 2600.  I had forgotten my Atari for many years.  In a stream of 16-bit computers, Japanese  consoles, and 386 DX computers, the glory of the old VCS was left behind.   However, seeing that video made me think of it again.   There were no video games in the video for Sabotage, but that was not the point.  It was the fact that this video made seem okay to dig into the past again.  I had spent so much time rushing through the old War 80's and and embracing the promise of the  90's, that I had forgotten how cool my childhood of the 70's had been for me.  Atari was a huge part of that.

Now, I can't say the video for Sabotage was the only thing start started me down this road of nostalgia, but it was certainly part of it.  This was still a couple years before video game nostalgia went mainstream, so  prices  of old equipment were still very low.  I checked the back of some magazines an saw that you could could buy a brand new Atari 7800 with 100 new games from a mail order place in Florida for about $125. Inspired,   I bought it as wedding gift for my wife and stored it until our big day a year later.

After that, I was hooked, and I've never stopped looking back as I looked forward either.

In a very big way, the Beastie Boys made nostalgia cool in the 90's, and it helped form the spark  I needed to find my roots again.

R.I.P. MCA, you will be missed.

Wow.  It seems like just a few years ago, we here at 8bitrocket.com were the only ones talking about using sprite sheets with Flash, and now Adobe has embraced the idea, adding support to export Flash animations as sprite sheets.  This is a GREAT feature that will help keep Flash on the top of the pack as an animation tool and game development tool.   CS6 has a ton of other improvements that move Flash CS6 into the realm of full-featured app development tool, but for today, we will savor the glory of the sprite sheet generator.