3 ms·
It could have been JavaScript 10 years before we had JavaScript. It demanded more dedication to use. Turns out round window with stroke path text alpha and rei
by ggm 7y ago
It could have been JavaScript 10 years before we had JavaScript. It demanded more dedication to use.
Turns out round window with stroke path text alpha and reimplemented xeyes was not compelling.
People should have shown NeWS doing complex client side form field checks.
Sun also didn't go downmarket. Windows PCs happened with hummingbird xceed X not decent in Microsoft X
- DanielKehoe 7y agoEvery day that I program in JavaScript I wish we had Display Postscript or NeWS in the web browser. Imagine if browsers had evolved with Postscript instead of JavaScript.
- masswerk 7y agoHowever, fashions in languages are a thing. While PostScript was hot by the mid 1980s, few were using it 10 years later, as there were now WYSIWYG PostScript editors like Illustrater, XPress, Page Maker, etc. Now, these were the days of C(++) and Perl, as may be observed in the JS syntax. But it would have been nice, if it had started with ECMA script (as opposed to LiveScript) and SVG had been already around.
- deleted 7y ago[deleted]
- tonyedgecombe 7y agoImagine if browsers had evolved with Postscript instead of JavaScript. Adobe would have a stranglehold on the market instead of Google.
- mhd 7y agoIt's not PostScript instead of JavaScript. It's PostScript instead of HTML, JavaScript and CSS. That's (IMHO) the more important point. One programming language to write and structure everything instead of a bastardized SGML plus a bastardized Java plus an ad-hoc config add-on. I'd much rather have (a slightly saner) JS for everything than PostScript plus HTML plus CSS, if I would have to choose.