Is HTML5 canvas capable of complex complex games like Flash?

Question

In addition, since a type such as HTML takes too much time, is it possible that <canvas> in HTML5, although it cannot be replaced in the specifications, will be updated frequently in the browser so that it can become better and better than Did Flash do / do in its various iterations?

In other words, we can have <canvas> in ten years, but today's canvas will not be canvas for five years, except for the name?

Answer 1

Not.

If you need to use the canvas on top of Flash, you should check what Grant Skinner did with the Create.js package - Easel.js is a very good attempt to model or approximate the Flash display model (containers, parameters, etc.), and with a decent JS IDE (hmmm) you can get some good stuff, but if you are a Flash developer, this experience is often rather depressing, does he like going back ten years and writing complex programs in JavaScript? Get ready for serious pain.

In explicit performance, the canvas has come a long way, but you still need to code in JS, you are missing the Flash IDE, which shaves weeks from development. Hopefully if we really have to accept this big mess in Flash, Adobe Edge will help.

In addition, HTML5 support sounds pathetic. Again, Grant Skinner and Audio.JS can suffer a lot, but, as with the display, large fragments of flash functions simply do not exist in HTML5, and there is no way to approximate them yet, as well as Yi Jiang points out (you can safely ignore another answer), any significant changes are time consuming!

Answer 2

The short answer, now and in the foreseeable future, is no .

First, you need to understand that this is not just the HTML5 we are talking about. Javascript is also needed for animation, game logic, 2D / 3D engine, etc. Although ActionScript performance is very low, Javascript performance is terrible compared to this. In addition, Flash has a mature and developed IDE and a set of drawing tools that allow you to create complex vector graphics and animations. As far as I know, there are no such things for <canvas> .

As for the specification, then again it is impossible. Adobe manages the IDE, language specifications, and client side for Flash. This basically means that they can do whatever they want with them. If you do not like any changes, do not buy / use their product. This means that they can develop their product in whatever direction they consider necessary, and at a pace that the W3C can never match.

HTML, on the other hand, is very different. The W3C should sit down with major browser vendors, as well as listen to web developers and end users. While critical, interesting features like <audio> and <canvas> are at the top of every web developer’s wish list, backward compatibility is also incredibly important for specs. This is one of the reasons that spec development is so slow - specs don't just depend on W3C deployment - they are also browser makers using specs, web developers using features, and end users updating their browsers. None of this will change with HTML5, so why do you expect development speed to be achieved?