My reasons for disgust at the lack of <canvas> in IE.
This is a response to: https://twitter.com/adrianba/status/2293950528
1) Charting and graphing. This is my major gripe. Developers should not have to use Flash, or Silverlight, or a bloated server side image tool, or 10,000 1x1 absolute positioned divs to show a simple graph that could be accomplished quickly and easily using <canvas>.
2) Pen/Tablet signatures, an example script could capture signatures from a tablet, and render them again later. It's fast and runs on machines that can not handle flash.
3) "Web Paint" kinds of apps, that allow users to create templates and drawings and render them again later. I'm forced to use workarounds or force users to use Firefox or Chrome for 2 nonpublic internal sites.
4) Simple kid games and coloring books are a snap to create. These kinds of for fun sites might seem unimportant, but it's not your job to tell developers their projects are not worthy.
5) Simple image editing, tweaks, labeling, rendering, etc.
6) SVG
7) Whatever developers want. The fact of the matter is, developers are using canvas for a lot of things, too many to list here. We're forced to either require any browser except IE, or provide hackish workarounds to emulate the canvas there.
Rant) Most modern browsers, like Firefox, Safari, Chrome and Opera, already support it. Microsoft as usual, lags behind forcing lots of workarounds. Why are we still doing this? Everyone else is agile with their releases, and constantly add support for new features. Not Microsoft's million dollar shop. They're slow to adopt. The only reason IE retains it's market share right now is because it comes on the box from the store, and many users are not aware of the options. That's slowly changing. When someone emails a "cool site" to their friend and the browser/site tells them that it IE isn't supported and they should switch, hopefully they will.
Comments (0)
tehuber.com
http://www.tehuber.com/article.php?story=iecanvas