4 ms·
The Xerox Alto, Smalltalk, and rewriting a running GUI (2017)
- yakz 1y agoIn person, on the real screen, is the font easier to read? I don’t understand why they didn’t go with something more… “plain”?
- neilv 1y agoI don't know, but I've wondered whether they were trying to signal or encourage (in demos or usage), that this was different, than familiar business computers.
- packetlost 1y agoI imagine it would look a lot nicer on a CRT vs rendered in high resolution on a LED display.
- kens 1y agoWell, the CRT on our Alto is pretty old, so the text is a lot worse in person. (That's why I used screenshots instead of photos.) But I think that even with a good monitor, the Smalltalk font would be quirky at best.
- sumim 1y agoThis font is called "Cream" and was designed and created by Bob Flegal to look identical on both screens and laser printers. cf. https://squeak-dev.squeakfoundation.narkive.com/Rs0CrNOk/font-history https://squeak-dev.squeakfoundation.narkive.com/Rs0CrNOk/fon...
- TheOtherHobbes 1y agoIt was the late 70s/early 80s, so a certain amount of twee whimsy was obligatory.
- deleted 1y ago[deleted]
- ChrisArchitect 1y ago(2017) Discussion then: https://news.ycombinator.com/item?id=15527726 https://news.ycombinator.com/item?id=15527726
- tho23i4324324 1y agoI'm generally shocked that people aren't profoundly shocked and saddened by what has been lost with these kind of "modifiable while running" systems like Xerox Alto and the Lisp Machines. Modern software frameworks are so shockingly bad and uninteractive that we now have to rely another layer of bullshit with LLMs just to get us to be half as productive as these envs. : ( (okay okay REPL-based things are getting better, but still nowhere close to what Lisp even w/ Emacs can do.)
- TheOtherHobbes 1y agoThat model stops working as soon as you try to distribute software at scale. You need some kind of standardisation and baseline. Otherwise your customisations conflict with someone else's customisations, with consequences that vary from mildly annoying to catastrophic. And the whole idea of shared software collapses. It would work if you had strict access control to each feature in a common code base. But Git hadn't been invented yet. The other issue is performance. Compiled ST isn't particularly slow, but you lose the modifiability. Interpreted ST has a mixed profile - some features are slow, some are fast - but generally it was slow compared to C. Today that doesn't matter so much, but it was a drawback at the time. It's a seductive model and I totally get the appeal. But it's not quite as straightforwardly superior as it might appear to be.
- wonger_ 1y agoDoes Erlang have these same properties? From what I hear, it works great for distributed systems and modifying-while-running.
- toast0 1y agoErlang systems don't do so well when multiple people are working on them with different understanding of what production is. (And especially if nobody actually knows). I don't know that you need 'strict access control' as proposed, but you do need coordination, and a source code repository is a way to manage coordination. Erlang doesn't have a different mode for fixed vs loadable code, although you may need to write code differently in order to be able to hotload changes, and that could affect performance; some code naturally fits the idioms needed though. I find it amazingly valuable to be able to change the program without having to lose the program state; but it requires different thinking, and it is easy to mess things up in exciting ways that are different than many other systems. It's amazing to fix a bug and deploy it in seconds into a live system with millions of active connections; it's also amazing when you try to fix a bug and break millions of active connections in seconds, but in a negative way, because now you and your users have to pay the costs of reestablishing all of those connections. OTOH, the key issue is interchange of state and messages between versions, and that's an issue that comes up in almost all distributed systems that update without downtime, so most people have to deal with that issue anyway, just usually not within the much smaller scope of a single task.
- ofalkaed 1y agoWhat is the best path for getting into Smalltalk these days? It seems like a good option for personal projects but never found much in the way of resources or even a good run down on Pharoh vs Squeak.
- deleted 1y ago[deleted]
- jdougan 1y agoProgramming a Space Shooter in Squeak/Smalltalk (Also has links to Squeak By Example) : https://scottgibson.site/ShooterGame/ https://scottgibson.site/ShooterGame/ A gentle introduction to Pharo Smalltalk (From the Glamorous Toolkit) https://book.gtoolkit.com/a-gentle-introduction-to-pharo-smalltalk-e4x65ty4hum90c23k84sgws1y https://book.gtoolkit.com/a-gentle-introduction-to-pharo-sma... Prof Stef (In Amber ST on JS): https://amber-lang.net/learn.html https://amber-lang.net/learn.html Immersive Object Programming course videos from INRIA: https://www.youtube.com/playlist?list=PL2okA_2qDJ-kCHVcNXdO5wsUZJCY31zwf https://www.youtube.com/playlist?list=PL2okA_2qDJ-kCHVcNXdO5... Pharo related books (links to Pharo By Example, etc.): https://books.pharo.org/ https://books.pharo.org/ Free Smalltalk Books: http://stephane.ducasse.free.fr/FreeBooks.html http://stephane.ducasse.free.fr/FreeBooks.html
- goodthink 1y agohttps://newspeaklanguage.org https://newspeaklanguage.org Smalltalk like, runs in a web browser, quite different.
- dang 1y agoThis post was part of a project that happened in 2017, the year that Alan Kay donated a Xerox Alto to YC. That was amazing but also challenging: what do you do with such a treasure? You can't just let it collect dust. After sweating a bit, we found a perfect answer and I think it's still valid today. What you do with something as precious as an original Xerox Alto, is you find someone as good as kens to entrust it to. Here's me describing the effort at the time: https://news.ycombinator.com/item?id=11930198 https://news.ycombinator.com/item?id=11930198. Ken ended up pulling in a brilliant bunch of volunteers (loosely grouped around the Computer History Museum, IIRC), and they eventually got the Alto working. Not only that but they made an incredible series of videos and posts along the way, so the rest of us could follow along. Once they'd gotten it working, we had a new challenge: what do you do with a working Alto? Again, the answer didn't take too long to figure out. What you do in such a case is you give it to the people who actually knew (and cared) enough to resuscitate it.
- dang 1y agoHere are the threads I found from back then—if anyone finds others, let me know! Fixing the Ethernet Board from a Vintage Xerox Alto - https://news.ycombinator.com/item?id=15636863 https://news.ycombinator.com/item?id=15636863 - Nov 2017 (29 comments) The Xerox Alto, Smalltalk, and Rewriting a Running GUI - https://news.ycombinator.com/item?id=15527726 https://news.ycombinator.com/item?id=15527726 - Oct 2017 (56 comments) Inside the vintage Xerox Alto's display, a tiny lightbulb keeps it working - https://news.ycombinator.com/item?id=15472747 https://news.ycombinator.com/item?id=15472747 - Oct 2017 (50 comments) Bitcoin mining on a vintage Xerox Alto: very slow at 1.5 hashes/second - https://news.ycombinator.com/item?id=14683326 https://news.ycombinator.com/item?id=14683326 - July 2017 (41 comments) Improvements to the Xerox Alto Mandelbrot drop runtime from 1 hour to 9 minutes - https://news.ycombinator.com/item?id=14637763 https://news.ycombinator.com/item?id=14637763 - June 2017 (63 comments) One-Hour Mandelbrot: Creating a Fractal on the Vintage Xerox Alto - https://news.ycombinator.com/item?id=14587915 https://news.ycombinator.com/item?id=14587915 - June 2017 (53 comments) Xerox Alto Restoration – Ethernet pioneers/founders of 3Com visit [video] - https://news.ycombinator.com/item?id=13138977 https://news.ycombinator.com/item?id=13138977 - Dec 2016 (35 comments) Restoring YC's Xerox Alto day 10: New boards, running programs, mouse problems - https://news.ycombinator.com/item?id=12714358 https://news.ycombinator.com/item?id=12714358 - Oct 2016 (13 comments) Restoring YC's Xerox Alto day 9: tracing a crash through software and hardware - https://news.ycombinator.com/item?id=12685593 https://news.ycombinator.com/item?id=12685593 - Oct 2016 (27 comments) Restoring YC's Xerox Alto day 8: it boots - https://news.ycombinator.com/item?id=12583554 https://news.ycombinator.com/item?id=12583554 - Sept 2016 (95 comments) Restoring YC's Xerox Alto day 7: experiments with disk and Ethernet emulators - https://news.ycombinator.com/item?id=12557777 https://news.ycombinator.com/item?id=12557777 - Sept 2016 (14 comments) YC's Xerox Alto restoration Part 7: disk exerciser trial [video] - https://news.ycombinator.com/item?id=12520795 https://news.ycombinator.com/item?id=12520795 - Sept 2016 (8 comments) Restoring YC's Xerox Alto: how our boot disk was trashed with random data - https://news.ycombinator.com/item?id=12507361 https://news.ycombinator.com/item?id=12507361 - Sept 2016 (50 comments) Restoring YC's Xerox Alto, Day 6: Fixed a chip, data read from disk - https://news.ycombinator.com/item?id=12482209 https://news.ycombinator.com/item?id=12482209 - Sept 2016 (31 comments) Xerox Alto restoration day 5: Smoke and parity errors - https://news.ycombinator.com/item?id=12437018 https://news.ycombinator.com/item?id=12437018 - Sept 2016 (1 comment) Xerox Alto Restoration Part 5 [video] - https://news.ycombinator.com/item?id=12427341 https://news.ycombinator.com/item?id=12427341 - Sept 2016 (13 comments) Restoring Y Combinator's Xerox Alto, day 4: What's running on the system - https://news.ycombinator.com/item?id=12197591 https://news.ycombinator.com/item?id=12197591 - July 2016 (35 comments) Restoring Y Combinator's Xerox Alto, day 3: Inside the disk drive - https://news.ycombinator.com/item?id=12072827 https://news.ycombinator.com/item?id=12072827 - July 2016 (21 comments) Xerox Alto Restoration Part 3: drive ok and First boot attempt [video] - https://news.ycombinator.com/item?id=12035108 https://news.ycombinator.com/item?id=12035108 - July 2016 (20 comments) Restoring Y Combinator's Xerox Alto, day 2: Repairing the display - https://news.ycombinator.com/item?id=12017354 https://news.ycombinator.com/item?id=12017354 - July 2016 (38 comments) “Hello world” in the BCPL language on the Xerox Alto simulator - https://news.ycombinator.com/item?id=11987324 https://news.ycombinator.com/item?id=11987324 - June 2016 (59 comments) Xerox Alto Restoration Part 2: Firing up the monitor [video] - https://news.ycombinator.com/item?id=11977215 https://news.ycombinator.com/item?id=11977215 - June 2016 (24 comments) Restoring YC's Xerox Alto, day 1: Power supplies and disk interface - https://news.ycombinator.com/item?id=11954920 https://news.ycombinator.com/item?id=11954920 - June 2016 (23 comments) Y Combinator's Xerox Alto: restoring the legendary 1970s GUI computer - https://news.ycombinator.com/item?id=11929396 https://news.ycombinator.com/item?id=11929396 - June 2016 (105 comments)
- pkphilip 1y agoHow similar is Pharo to this whole experience?
- frou_dh 1y agoCuis Smalltalk seems to be the keeper of the old Smalltalk experience: https://cuis.st https://cuis.st https://cuis.st/features https://cuis.st/features Pharo is like enterprise-grade, bells and whistles galore.