Lmst

Chuck Geschke was a #XeroxPARC employee, #pioneer of #computergraphics, #WYSIWYG, and page-description languages. As co-founder of Adobe Systems, father of #PostScript and #PDF-files* the impact of his work is literally everywhere. (*not to be confused with pedophiles like Jeffrey Epstein)

In this oral history session he's talking about the Jesuit order, #Xerox, #InterPress, #vectorgraphics, #DTP, and...
https://youtu.be/dlx7sGG4lxo

Our #portrait of him is made in #SVG #vector #graphics with #Inkscape, of course. Even the female #demographics are #traced by hand in this amazing tool of #FreeSoftware & #FreeDownload. NO #ToS-scams, NO #creativecloudBS, NO #AI, NO obstacles for YOUser's to be #creative — here...
https://inkscape.org

Portrait illustration of Chuck Geschke presenting Adobe Illustrator with graphic (almost explicit) examples. Created in SVG with Inkscape, not old proprietary software.

How the developers of Bravo at Xerox PARC overcame the limitations of Alto to design the first WYSIWYG editor and make it run efficiently.

http://billverplank.com/CiiD/Bravo-Newman.pdf

#XeroxAlto #XeroxPARC #retrocomputing

I've seen this image a bunch (70s kid programmers at PARC), but now I want to find the source of the posters on the wall behind the computer.

Image source: https://computerhistory.org/blog/introducing-the-smalltalk-zoo-48-years-of-smalltalk-history-at-chm/

#xeroxPARC #Smalltalk #computerHistory #RecodeProject

Children animating horses in Smalltalk-72 on an Alto computer. Courtesy of the PARC Library. © PARC. CHM Object ID 500004466

ᐅ The Alternate Reality Kit

https://youtube.com/watch?v=w1HhPE0zV6g

#XeroxPARC #Smalltalk80 #IDE #Retrocomputing #Retrodev

Remembering Lynn Conway for her pioneering work leading to VLSI and her personal fight against transgender discrimination

https://hackaday.com/2024/06/14/rip-lynn-conway-whose-work-gave-us-vlsi-and-much-more

https://ai.eecs.umich.edu/people/conway/LynnsStory.html

#VLSI #computerhistory #conway #transgender #ibm #xeroxparc #womenincomputing

A remarkable life: "Lynn Conway, leading computer scientist and transgender pioneer, dies at 86".

https://www.latimes.com/business/story/2024-06-11/lynn-conway-leading-computer-scientist-and-transgender-pioneer-dies-at-85

#lynnConway #ibm #xeroxPARC

TIL why the default Ethernet MTU is 1500!

#Ethernet #ComputerHistory #XeroxAlto #XeroxPARC
https://exple.tive.org/blarg/2024/04/24/magic-numbers/

Can Xerox’s PARC, a Silicon Valley Icon, Find New Life with SRI?

https://www.nytimes.com/interactive/2024/03/26/business/silicon-valley-tech-xerox-parc-sri.html?ugrp=c&unlocked_article_code=1.j00.dH0_.CTy-FNLqj2rc&smid=url-share

"Two research labs known for some of the tech industry’s most important innovations have merged in hopes of recapturing their glory days." -- #JohnMarkoff

#WWW #XeroxParc #SRI

Dealers of Lightning: Xerox PARC and the Dawn of the Computer Age by Michael A. Hiltzik (1999)

Text instead of screenshots: https://cohost.org/lurkjay/post/5166294-dealers-of-lightning

#reading #nonfiction #books #history #technology #engineering #computers #PersonalComputer #xerox #XeroxPARC #XeroxAlto #bookstodon

Thacker reasoned that if each of the computer’s routine tasks could somehow be ranked by urgency and funneled through the processor in appropriate order, he could keep the processor occupied almost full-time. If the ranking was correct, every task would be handled when it needed to be, no sooner and no later. Low-priority tasks could be interrupted for brief periods to make way for more urgent ones, then resumed later, when nothing more pressing was in the way. The gain in efficiency, speed, and hardware was potentially huge. Whole circuit boards that served as the ancillary brains of disk drives and other units could be dispensed with. The Alto’s CPU would be drafted into doing the thinking for all of them.

Thacker’s second crucial inspiration involved the question of how to power a high-performance display without busting the budget on memory. This was not trivial: He understood that the quality of the display would make or break his new computer.

Up until then, computer designers wishing to provide an interactive display faced two equally unappetizing choices: They could give the display little memory support, which led to flickering and slow performance, or they could provide backup memory through a character generator, which meant burdening the system with another and bug-prone peripheral the size of a washing machine.

Thacker struggled at length with the riddle of how to direct a suitable volume of information to the screen without adding excess hardware. The answer came to him one day while he was watching a demonstration of one of Kay’s graphics programs in the Systems Science Lab.

The demo utilized a character generator designed by a former Engelbart engineer named Roger Bates (with Lampson’s assistance). This unit, which had thousands of dollars’ worth of memory inside, was a distant relative of the one Ron Rider would later build for the SLOT. It was designed to store custom fonts by allowing each character to occupy a small rectangular patch of memory until summoned to the screen. Most of the PARC engineers considered it a disappointment, largely because the designers’ ambition to reproduce book-quality pages on the POLOS screen turned out to be a tougher programming challenge than they anticipated.

Kay’s group was an exception. Bored with the idea of painting text on the screen but fascinated with the possibility of displaying images, they had appropriated the system—“perverted it,” in Lampson’s unpejorative phrase—to use for their graphics and animation programs by loading its memory not with print characters, but graphical designs.

The result was a rudimentary black-and-white “bitmap”—a block of memory in which each bit corresponded to a dot on a display screen. Flip a given memory bit “on” and the corresponding dot lit up on the display; turn on these bits in a given pattern and you could map the same image to the screen.

As Lampson explained, “In the normal deal there would be a little bitmap for the character ‘A’ in the font memory and a bitmap for ‘B’ and ‘C’ and so on, and then the character memory would say display an ‘A,’ an ‘h,’ and an ‘a,’ and aha, you have ‘Aha.’ Alan said, ‘We’ll have a whole bunch of artificial characters numbered 1 through 500, and the character memory will say display 1, then 2, then 3.’ The result was to take the font memory and turn it into a bitmap”—that is, well before the lab had the resources to build a full-scale bitmap.

Kay’s group had only begun to investigate the potential of this new way of displaying information (although they had done enough to help persuade Thacker and Lampson of the need to equip the Alto with a high-resolution display). Among their first simple programs was one that could embed “icons,” or thumbnail-sized pictures, within blocks of text. Another was a painting system in which users wielded square “brushes” up to four pixels wide to draw or erase lines and curves on the screen.

Impressed as he was by these applications, Thacker was struck more by the underlying principle by which Kay’s system used the memory blocks.

He realized that just as Kay’s team had turned the character generator into a simple bitmap, he could convert idle blocks of the Alto’s main memory into a bitmap for the display screen. Forcing the memory to perform this double duty would eliminate the need for a separate character generator. This required cutting a few corners, because the display would now have to compete with all of the machine’s other functions for memory blocks. When the Alto placed a text document on its screen, for example, it would economize by omitting from the bitmap any part of the page that lacked text, such as the white spaces between lines and at all four margins. Also, whenever there were competing demands for memory from data and display, the display lost. Users had to be alerted to expect a strange phenomenon: During a work session the image of the document they were writing or editing would gradually shrink, like a window shade rolling up from the bottom. The reason was that as the increasing volume and complexity of the data claimed more memory, less remained for the bitmap. The same phenomenon accounted for what happened whenever the Alto displayed a full-screen graphical image. On those occasions it tended to run agonizingly slowly, in part because so many processor cycles were consumed in painting the screen, but also because the display consumed so much memory there was barely enough left to keep the program percolating along.

https://spectrum.ieee.org/smalltalk

#smalltalk
#stevejobs #apple #computerhistory #xeroxparc

“The destiny of computers is to become interactive intellectual amplifiers for everyone in the world pervasively networked worldwide”.

https://www.quora.com/What-made-Xerox-PARC-special-Who-else-today-is-like-them/answer/Alan-Kay-11

#AlanKay #jcrLicklider #darpa #xeroxParc

Today’s find, from under my bed, from I-don’t-know-how-many-thousand years ago, while looking for my new cat #papers #xeroxparc

Butler W. Lampson’s legendary paper titled Hints for Computer System Design

@jaruzel @StefanoGaivota interesting! To me, #retrocomputing covers early #eightbit (and #sixteenbit) personal computers, and #vintagecomputing covers #mainframe, #minicomputer and #workstation machines (the latter category being composed of #LispMachines, graphical #unix workstations and of course the #XeroxParc machines).

thinking about the magic ingredients that foster #tech #innovation. #XeroxPARC, #BellLabs, and #MIT's #TMRC appear frequently in the annals of #history - at least those I've read.

The #question is - how do we create such centers of innovation?

I'm still putting it together but I suspect there are at least four:

1 Time- Insane and copious amounts of it
2 Community- Multiple individuals who interact syngeristically
3 Space- A shared space for innovation to occur
4 Equipment- Raw materials

1/5

The decisive influence of women on the development of #LispMachine processors and #Scheme in general is criminally under-discussed:

"We had heard that Lynn Conway from Xerox and Carver Mead from Caltech were making real progress on making it possible for people who were not at a chip-fab facility to specify chips for experimental designs. In the Spring of '78 we invited Lynn Conway to teach the class on #VLSI design that she was working on with Carver Mead. Just a few years earlier Guy L. Steele Jr., (then my graduate student) and I invented a simplified but elegant version of the #LISP family of languages that we called Scheme. Guy and I wrote a number of internal memos (Lambda the Ultimate...) that later became famous. Guy enrolled in Lynn's class. For his term project he designed and fabricated a direct interpreter for Scheme, called Scheme-78. It didn't quite work (because of three missing wires); it didn't have a garbage collector; and it was too small to do anything impressive; but it encouraged us to try again. Over the next few months Guy Steele, Jack Holloway, and I designed a new interpreter that we thought could actually be run on a real memory and tested with real programs. I designed the register array, Guy and I developed the microcode. Jack made a PLA generator that could hold the microcode, and we roped Alan Bell of #XeroxPARC into assembling the Scheme-79 Chip. We pulled this off in a few man-months of time and it worked! Scheme-79 had a mark-sweep #GarbageCollector with a Deutsch-Schorr-Waite mark algorithm and a two-finger compacting sweep. It also had a two-level microcode: The main PLA contained rather high-level microcode instructions that were further elaborated by a nanocode PLA that operated the register array.

Further encouraged, I started a new project to make a chip that was actually big enough and fast enough to be useful to run real research programs. This was the Scheme-81 chip. It was a 32-bit machine, with 6 bits of type code and 26 bits of address. It had microcode support for everything required to make a Scheme computer operating system, including a stop-and-copy garbage collector, a coprocessor bus, and an interrupt system. For Scheme-81 the microcode was written by Richard Stallman, Chris Hanson, and me. (Steele had graduated and moved on to CMU as faculty.)"
- Sussman

#WomenInTech #TransPride #lgbt

https://www.artsy.net/article/ruse-laboratories-gerald-jay-sussman-creator-of-scheme

A great paper from 2004 by Richard P. Gabriel (Lucid, Inc.), Jon L White (ditto), Daniel G. Bobrow (Xerox PARC) that explains how Common Lisp Object System integrates functional and object-oriented programming: https://dreamsongs.com/Files/clos-cacm.pdf

#Lisp #CommonLisp #CLOS #MOP #OOP #ObjectOrientedProgramming #FunctionalProgramming #Metaprogramming #Programming #ProgrammingLanguages #PLT #XeroxPARC #PARC

https://youtu.be/pQocN_c2uLI
The Xerox Thieves, Steve Jobs and Bill Gates. #Xerox #XeroxPARC #GUI

All about Xerox PARC from The Chip Letter.

PARC is one of the richest slices of computing history. And the mentioned Hiltzik book is one of the best computing history books I've read.

https://thechipletter.substack.com/p/chip-letter-links-no-21-xerox-parc

#XEROX #PARC #XEROXPARC #computinghistory #computerhistory #UNIX #smalltalk #GUI #mouse #Apple #vintagetech #techhistory #history #blog #video

A bunch of old videos from Xerox PARC just got dumped on the Computer History Museum's YouTube channel. This is just one of them. Really neat stuff. #RetroComputing #XeroxPARC youtu.be/rR_24-_83-o

I intervjuet forsøker Kristen Nygård å forklare objektorientert programmering (#OOP).

I tillegg til Ole-Johan Dahl så nevnes Alan Kay, Xerox PARC, #SmallTalk og Apple Lisa (skrevet som LISA). Endel unøyaktigheter er det i teksten, f.eks. Alan Kay skrev ikke SmallTalk alene, men det er vel ikke så galt til å være et reklameblad.

#AlanKay #XeroxParc #AppleNytt #Simula #OleJohanDahl #Macintosh #norsktut #allheimen

#xeroxparc

Client Info