107 karma · joined November 11, 2014
https://smurp.com/
The Blue Book (Tutorial and Cookbook) https://archive.org/details/postscriptlangua0000unse
The Red Book (Language Reference) https://archive.org/details/postscriptlangua0000unse_l1h3
The Green Book (Language Design) https://archive.org/details/PSGreenBook
My other PostScript stuff was mostly fun and experimental: some fractal hacks which made printers and typesetters groan and some collaborative knowledge visualization stuff. I got started with PostScript on my NextStation in 1991 and it served me well, being the basis of a whole career of programmatic visualization.
Adjacent (resilient, low-level, big-vision, auditable) projects include:
http://collapseos.org/ Forth OS, bootstrapable from paper, for z80
https://urbit.org/ standalone, distributed, auditable, provable, minimalist
https://justine.lol/ APE (actually portable executable); cosmopolitan libc
To staunch any other niggling, I am neither sure of the year nor whether that property was bearing the K-Mart branding at that time. It has also been a Zellers and a Target, if memory serves.
This coverage does a poor job of conveying whether he could tell that the craft was climbing, though evidently it was. A crucial detail in his situation was whether the vehicle was responding to his control directions and whether its trajectory was upward, hence without an immediate threat of crash. There is a faint indication that he should have known that his aircraft was in fact climbing and that, as a consequence, he was going to have time to problem solve.
It sounds like the group he led is tasked with establishing the limits of and determining the norms for the operation of the various craft they fly. This suggests that a greater spirit of discovery and exploration of the letter of the rules was in order than he happened to exhibit on that occasion.
He had that command taken away, not his flight privileges, because the shortcoming he exhibited was indicative of his personal unsuitability for exploring the limits of his vehicle and the policies for its operation — in short for doing that particular, exceedingly demanding job. He gets his choice of other posts, but not continuing that crucial and complicated role for which he evidently did not have the right stuff. No shame. Peter Principle avoided. Everybody did the right thing, including his commanders.
I used to dream in PostScript I was coding in it so much -- the experience was dreaming about stack-oriented coding, as opposed to vector visuals, for clarity. I got started coding in PS on the NeXT in '91 doing data driven graph visualizations. PS was great for some algorithmically-generated logos too. Really fun were some fractals which strained the imagesetters and printers they ran on. Learning PS really paid off though when I ended up using it to create a database publishing engine for real-estate listings. It used Python for data wrangling and orchestration and then PostScript for the dynamic book generation and layout. It was used back when real estate agents relied on giant books printed daily, which this engine generated for dozens of markets across Western Canada. These documents were pretty gnarly too, including property-type-specific templates, various indexes, property images, market-specific variations, etc -- and doing all that with the absolute control which PostScript permitted was fantastic. It would have been nightmarish to try to do such things in LaTeX, Word or the DTP tools of the era. PDF rendering was automated with GhostView so the whole toolchain was open source.
I'd suggest that if extreme precision, detail and complexity are your requirements and especially if rendering to PDF and screen bitmaps are needed then PostScript is still very relevant. It's also quite fun as a developer.
In the sentence "With the theory physicists Gregory Breit and John Wheeler were able to prove that when two high-energy photons collide, a positron and an electron arise, i.e. matter is formed" shouldn't the word be "predict" not "prove"?
A more flagrant example of a strange word choice for a human science writer to make is "A direct conversion would require a laser that emits gamma-ray photons in a highly concentrated steel." Shouldn't the word "steel" instead be "beam"? This seems like the sort of thing an uncomprehending bot might do, conflate those two words.
Are my the nits I've picked, above, unfounded? Does the author of the original paper have any information which might suggest that an actual human wrote the "Science News" piece?
If not I would suggest that we've got a bot on the loose! Eeek!
Further, I think I'm seeing rather a lot of "content" floating around recently which smacks of machine origins.
Also, to Daniel... Great paper. Amazing stuff!
while true; do curl -s https://status.github.com/api/status.json | egrep 'good|minor' && say -r 160 "github is up again" || echo -n .; sleep 60; done
Edit: accept a status of minor as an indication of up-ness.