4 ms·
In that case why didn't the broader community adopt PostScript for the web? Was it because of technical reasons (too feature heavy and complex for HTTP as envis
by Santosh83 6y ago
In that case why didn't the broader community adopt PostScript for the web? Was it because of technical reasons (too feature heavy and complex for HTTP as envisioned originally) or did Adobe have some kind of patent that prevented its free use?
- jandrese 6y agoThe most direct answer is that browsers didn't include PostScript support. They had their hands full trying to beat JavaScript into shape, they didn't want to support a completely different second language. Nobody was clamoring for PostScript support either. The advantages would have been fairly minor for the massive amount of work it would have taken to not only implement the browser support (both in Navigator and IE) but also for web developers to learn an entirely new language and create content in it. I guess there could have been a use case for people typesetting their documents in Word or LaTeX and then "printing to web", but PDF took that role.
- a_e_k 6y agoAdobe had been pretty open with PostScript. From the PostScript Language Reference, 3rd Ed: > However, Adobe desires to promote the use of the PostScript language for information interchange among diverse products and applications. Accordingly, Adobe gives permission to anyone to: ... Source: https://www.adobe.com/jp/print/postscript/pdfs/PLRM.pdf#page=24 https://www.adobe.com/jp/print/postscript/pdfs/PLRM.pdf#page...