On Tue, Jul 7, 2009 at 11:37 AM, Hans Schmucker <span dir="ltr"><<a href="mailto:hansschmucker@gmail.com">hansschmucker@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I should really add one point. The Canvas spec, above all, is<br>
predictable. You pretty much know exactly what you'll get when you<br>
perform certain actions.</blockquote><div><br>Like arcTo?<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Relying directly on SVG filters makes things<br>
harder to understand and predict. A flat, stripped-down API</blockquote><div><br>APIs don't remain stripped-down for long.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
If you directly include SVG, a developer who wants to use it has to<br>
understand all of SVG,</blockquote><div><br>That is completely untrue.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">which is a pretty big spec, with lots of<br>
unexpected behaviour. And as a result, often incorrect behaviour in<br>
implementations.<br></blockquote><div><br>Yet you're asking us to duplicate code, which inevitably leads to even more bugs.<br></div></div><br clear="all">Rob<br>-- <br>"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]<br>