Now they meet downtown. I have no other reason to be there, I don't drive, barely walk, and am afraid of air. I should be writing a program that works, but instead…
This page contains what is left of the presentations I made to the WLUG. (Some of it has been changed or deleted over the years.)
The day comes. I try to log on jit.si at 7pm. … Waiting for moderator. Try log on without one, it presents three choices: Facebook, Google, Github.
Epic fail. I finally get into the meeting about 20min late. They are talking about something to replace Twitter (the formerly known web site). To me, that's like asking for a replacement for poison ivy. I never touch it.
I rudely interrupt and try to present my slide show, but screen sharing does not seem to work like it did last time. I want share my whole screen. I think I did that last time. The plan was to demo the program by showing slides in one window, an emacs instance with TeX source in another, a shell prompt from which I can show how to run the program in another, and the result in another.
I didn't take notes, and don't remember exactly what happened, but I think when clicked the "share screen" it popped up a two item menu with something like "share whole screen" or "share one window", but the "whole screen" choice was dimmed and nothing happened when I clicked it. I could only share a web browser window.
I can't edit and run programs in a web browser. The slides were made to go with that planned demo; they aren't worth much without it, but here they are:
PDF Slides
and here is the souce code:
LaTeX source for Slides
I don't remember where I got it. The file on my machine is dated 2011-Jun-10. It's probably a copyright violation, and it's bigger (408K) than the average cartoon, so keep it on the down-low.
I thought of re-compressing it to save bandwidth, but I think there might be jokes that I don't get written on the post-it notes stuck around the screen. Take your copy for personal use, zoom in, and let me know if you see anything funny.
*** Emacs user at work cartoon. ***
At least since Ken Thompson's Turing Award Lecture "Reflections on Trusting Trust" it has been known that (by Kleene's Recursion Theorem) it is possible to put a trojan horse into a compiler in such a way that it can neither be seen in the source code of the compiler, nor removed by re-compiling the compiler.
I made a presentation for the Worcester Linux Users Group (WLUG) last year. I continue to think about these things. I'll let you know when I make notable progress.
Update (2024-11-23): Obviously that was written in 2020, the year it all fell apart. The presentation was done at WPI. I made the slides for the 2024 November presentation by copying and changing these. I was worried for a while that it would be too repetitious, but students who were there are now graduated. In 2019 I used LaTeX; in 2024 I talked about it. Doug Waud did a presentation on TeX, but the undergraduates now weren't born then. Repetition is good and it is good to review again.
I made some slides using LaTeX to produce PDF files and showed the webpage of the source-only bootstrap project.
PDF Slides
Source only Bootstrap
Then I did a demonstation of these programs:
A self-reproducing C program
Polyhedronism
TeX←Scheme
|
This page is standard validated HTML 4.0. ( Checked 2022-01-14) |