John Warnock's "linguistic motherboard" and Owen Densmore's "class.ps" smalltalk-like object oriented PostScript programming system, which NeWS and The NeWS toolkit used.
Owen Densmore's work with Bill Atkinson and John Warnock on the Mac printing system, and his "linguistic motherboard" email and "Swiss Army NeWS: A Programmable Network Facility" white paper:
My boss, many years ago, talked about the time he programmed a printer to act as a web server using Postscript. I never asked what happened to other print requests while it was running.
There is an apocryphal story about some poor sys-admin who after spending several days trying to diagnose mysteries hangs in the new office laser printer. traced it to one user who was sending long print jobs that printed nothing. This enterprising engineer had to be told to knock it off after explaining how the new laser printer had the most powerful computer in the office and as such had rewritten some of his simulation code in postscript to run on the printer.
They were routed to the integrated time machine in PS, and sent to the year 2026 when they would be rendered in mobile phones, then the bitmaps would be sent back in time to your boss's printer.
Check out Don Lancaster’s tinaja archive, if it’s still around. He was quite enamored with NeXT style universal postscript and wrote at length about it.
DonHopkins on July 1, 2023 | parent | context | favorite | on: Don Lancaster has died
I have always been a huge fan of Don Lancaster's wizardly writing about PostScript, who not only regularly published in Computer Shopper, but also generously ran a free PostScript help line at his own personal phone number. But Woody Baker was by far his biggest most enthusiastic fan of all (and highly eccentric in personality and coding style), and he would regularly extol and evangelize Don Lancaster's virtues and ideas on comp.lang.postscript.
Once around March 4 1990, I gave Woody Baker some feedback on his comp.lang.postscript faq, including the suggesting that he might consider leaving Don Lancaster's personal phone number out of it, but he replied:
>Again, I want to thank you for your contributions. You and D. Cortesi have been most helpful. The two of you gave me very in depth feedback. I have moved almost all the editorializing to the end. I have moved the style stuff to the end. As for DON LANCASTER, I left his phone number in. Don publishes it regularly in the computer shopper, as a free PostScript help line. He is self-employed, and a widely published Author, for TAB books among other things. He says he averages 80 helpline calls a day. He also sells programs and books that he is self publishing. I can assure you, he won't mind at all.
Woody loved to talk in depth about how amazing and inspirational Don Lancaster was, and defend his well deserved honor and reputation whenever anybody criticized his work.
>True. Don lives in an APPLE II world. You are wrong, however in certain statements. He has (unfortunatly) mentioned what FLXPROC does. It happens to be critical to certain things, that several consultants are working on here and there. He knows enough not to blab some things, and jerk work out from under individuals (at least some of the time). Don has dug pretty deeply into certain areas of PS, and I have dug deeply into other areas of PS. Don is first and formost a writer. He's self employed, and extremely intellegent. I am first and formost a software engineer, and secondly a writer. I tend to write, however for clients. I'm confident that I know what FLXPROC does, and what it is good for. And I'm sure Don does also. I more or less told him about FLXPROC and he more or less told me what it does. After first quarter 1990, some things will be essentially worthless as consulting info, and will rapidly become public knowlege. I don't applogize for keeping the lid on some things. I'm a bit of a mercenary in a way. I like consulting.
>Copyright c. 1987 by Don Lancaster and Synergetics, Box 809, Thatcher, AZ 85552. (520) 428-4073
>Electronically self-published using the Apple //e computer and the LaserWriter Plus. All graphics were done in their entirety by ProDOS Applewriter 2.1.
[...]
>I don't think I was ever more amazed when Woody Baker of The Copier Store mailed me back one of my very own laser printed business cards — redone in real ink in an almost "embossed" gold! Turns out Woody had found an older Omnicrom machine scunging around unsold in the back of his warehouse and fired it up. Lo and behold, the instant conversion of any toner image to real ink in stunning colors!
Example 10 of Don Lancaster's Postscript Show & Tell beautifully illustrates how an Omnicrom printer works:
>Example ten -- What appears hear as a mild-mannered Postscript technical illustration is really the secret of full color laser printing.
>Omnicrom sheets are real ink applied to a carrier. You place the sheet in contact with your toner image and then run it back through the fusion rollers a second time. The ink gets fused over the toner.
PostScript was the first language I ever used professionally! :P
At the time, I worked for a printing house in Kyiv that specialized in accidental printing (screen printing, flexo-, tampo- etc. i.e. mostly printing on weird curved surfaces, not paper). The triad (full-color) screen printing was all the rage (early-mid 90s). Part of the process of generating the films that were later used to irradiate the polymer layer covering the screen mold was bound to a bootleg Scitex machines IDF used for printing maps. While we had the machines, we didn't have a proper driver that could take a color image, separate it into channels and instruct the machines to produce the films. So, I'd produce PS files from, eg. Photoshop (also bootleg...) and then edit the PS files by hand to match the requirements from the Scitex machines.
I wasn't a programmer by training, and doing all this stuff absolutely felt like magic. Something I will never experience with computers again :'(
Per WSJ, previously, they both had revenue sharing agreements. MSFT will no longer send any revenue to OpenAI. OpenAI will still send revenue to MSFT until 2030 (with new caps)
My understand was that was in relation to IP licensing. Microsoft got access to anything OpenAI built unless they declared they had developed AGI. This new article apparently unlinks revenue sharing from technology progress, but it's unclear to me if it changes the situation regarding IP if OpenAI (claim to) have achieved AGI.
I wouldn't be surprised if they had already, internally. An OpenAI employee tweeted today that Codex has achieved "escape velocity" and is now improving rapidly. Make of that what you will.
The point is also that you don't have to sign up for AWS, and GCP, and Azure, and Alibaba, and Nebius…
And, more importantly, that you can use the existing OpenAI SDK for your language but swap models (even across providers) by changing one line of code.
You're paying for convenience, yes, but model routers solve a real problem.
Using its own TERM is a deliberate design decision. I don't remember how to fix the terminal database, but it's pretty easy (your favorite search engine or LLM should be able to help you there).
If I install a terminal and SSH doesn't work from it out of the box, I would describe that as a bug and wonder if I need to read the full manual to not fall foul of other gotchas
Servers throwing "missing or unsuitable terminal" even when the connecting terminal is available and very suitable. And this is just because they hardcode xterm as the "standard".
I definitely have had to poke at things a bit, even where they "should" work. I use salt in my homelab and eventually got the xterm-ghostty.terminfo file and I put it in my baseline salt config, then you run 'tic -x xterm-ghostty.terminfo'.
People must really love PostScript!
reply