Re:How Scribd runs 150,000,000 polygon intersections a day
by petervandijck on Thursday June 24, 2010 @09:14PM
(#1459694)
ok that's crazy. Is scribd becoming the new pdf (I mean that in a good way)?
[ Parent
| on HN ]
Re:How Scribd runs 150,000,000 polygon intersections a day
by ary on Thursday June 24, 2010 @09:26PM
(#1459713)
The only thing I could applaud more would be a new (and simpler) cross platform document format (for asset encapsulation and offline viewing) that could be transformed to and from HTML on a whim. Scribd <-> My Screen <-> My Printer. To death with PDF.
Come to think of it HTML5/CSS3 + an open archive/compression format would suit this purpose nicely.
Re:How Scribd runs 150,000,000 polygon intersections a day
by tomjen3 on Friday June 25, 2010 @08:41AM
(#1460570)
What is your problem with PDF?
Almost any browser other than lynx has a buitin pdf reader, and pdf can be created by just about anything.
Finally pdf is a format that allow you to ensure that no matter where it is printed, it is exactly as you wanted it to be.
Re:How Scribd runs 150,000,000 polygon intersections a day
by gruseom on Friday June 25, 2010 @12:25PM
(#1461205)
The problem with pdf is that everything about it is clunky and slow. I didn't decide to groan whenever I see that something I want is trapped inside a pdf; years of annoyance just built that up as a reflex.
Edit: actually, there is an exception, and you mentioned it: printing a pdf, once you have it open, is almost always a good experience. Too bad it's the thing I want to do least often.
Re:How Scribd runs 150,000,000 polygon intersections a day
by ed on Friday June 25, 2010 @05:13AM
(#1460350)
You've just described ePub.
Re:How Scribd runs 150,000,000 polygon intersections a day
by ary on Friday June 25, 2010 @11:58AM
(#1461116)
I'm looking for visual and layout consistency across all mediums (screen, print, etc) and in my experience ePub isn't suited for that. My apology for the lack of clarity.