|
|
|
|
|
by drivebyacct2
5708 days ago
|
|
Why? If it is truly "in HTML5"... that implies there is not a server side component. If it is just grabbing the drawing from canvas and submitting it to the server, I'm not really impressed. And considering how slow it is now, I'm not sure what exactly to think. :/ edit: Yup, a quick run with Chrome shows that it is just sending a list of the strokes to the server. It explains the speed. I'm more interested in the algorithm (and why it wasn't ported to client side JS. That would made for a much more impressive showing and a lower hosting bill). |
|
As a full match database may well weigh in at a few hundred megabytes (pure speculation here), schlepping it over to the client would make for a must less impressive showing and a higher hosting bill.
(As fun as it would be to "view source" for it, or have it work offline.)