Linked by Thom Holwerda on Mon 12th Mar 2012 22:21 UTC, submitted by deadwood
Thread beginning with comment 510378
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
More News »
Sponsored Links



Member since:
2010-03-08
See it this way : to display HTML5, you just need to port some of the dozens of open-source web browser rendering engines out there, put a simple frontend around it, and you're done. It won't be pretty, but it should do the job well enough to advertise "HTML5 compatibility". Prerequisites do not go much beyond having GUI ready.
To print, now, you need a lot more infrastructure work : not only GUI, but also a printer driver model, printer drivers themselves, code that allows application code to talk to printers, GUI that makes it easy to do, all that knowing that as with any infrastructure work, the silliest mistake will follow you across the OS versions to come due to the need to maintain driver and UX compatibility (whereas with a web browser, you can just ditch the old rendering and replace it with another one and users won't even notice).
The two tasks have a similar "wow, this OS is grown-up now" factor, but printing is an order of magnitude more complex to implement. It is as such logical that it comes second, unless it is a priority to developers.
Edited 2012-03-13 07:49 UTC