9 ms·
A Look Back at the 1960s PLATO Computing System
- walterbell 9y agoFrom the article: "Imagine if today, iOS or Linux had built-in libraries of code that allowed anyone to build a social application that didn’t require cutting a deal with Facebook or using their APIs,” … “[With PLATO], the API was in the operating system and it allowed any app to be social. … Term Comment … allowed users to leave feedback for developers and programmers at any place within a program where they spotted a typo or had trouble completing a task … the user would simply open a comment box and leave a note right there on the screen. Term Comment would append the comment to the user’s place in the program so that the recipient could easily navigate to it and clearly see the problem, instead of trying to recreate it from scratch on their own system … “If you were doing QA on software, you could quickly comment, and it would track exactly where the user left this comment. We never really got this on the Web, and it’s such a shame that we didn’t.”
- goatlover 9y agoMakes you wonder what pioneers back in the 60s and 70s could have accomplished with modern hardware. What does Smalltalk or Englebert's NLS end up being with gigs of RAM and high speed network connections? What would the LISP machines have been like? It still kills me to think that an OS crash on one of those took you into the Lisp debugger. And it kills me to think that Smalltalk and Visual Basic had a built-in GUI editor and layout manager, unlike the web.
- SllX 9y ago> What would the LISP machines have been like? It still kills me to think that an OS crash on one of those took you into the Lisp debugger. Sometimes I think a lot of people do use LISP machines. It's just called emacs. I joked on here once that I think the end game for GNU/HURD was ultimately to become a LISP machine via emacs, and if you look at some dev setups, that's not too far from what macOS and Linux are for them today: a place to run emacs and a web browser.
- pjmlp 9y agoIt is not the same thing. Emacs is a tiny portion of what a Lisp Machine was capable of.
- jacobush 9y agoI don't doubt you, but could you be more explicit?
- pjmlp 9y agoLisp Machines REPL was graphically based, not text based. So the REPL could display any kind of data structure, and later calls could influence already displayed data. https://www.youtube.com/watch?v=o4-YnLpLgtk&t=687s https://www.youtube.com/watch?v=o4-YnLpLgtk&t=687s https://www.youtube.com/watch?v=6uPwQuxjgQo https://www.youtube.com/watch?v=6uPwQuxjgQo https://www.youtube.com/watch?v=IMN5RSIm6xw https://www.youtube.com/watch?v=IMN5RSIm6xw There was GUI based debuggers. Then there was the access of the complete OS stack and other running applications, and everything was compiled to native code, there wasn't any VM running. Try do do a (disassemble func) on Emacs for seeing actual 80x86/ARM,....
- jacobush 9y agoThe problem for me with Emacs is that (while I use it everyday for just about all editing, and recently org-mode) it's so damn brittle and hard to configure. It's like editing autoexec.bat on DOS and reboot to try your settings. Still, it's the best I've found.
- pjmlp 9y ago> Makes you wonder what pioneers back in the 60s and 70s could have accomplished with modern hardware. One of the best Bret Victor talks is about that. "The Future of Programming" https://www.youtube.com/watch?v=8pTEmbeENF4 https://www.youtube.com/watch?v=8pTEmbeENF4 > And it kills me to think that Smalltalk and Visual Basic had a built-in GUI editor and layout manager, unlike the web. Anyone of us doing desktop/mobile development on .NET, Java, Android, iOS, Qt development can still enjoy such goodies. With web, one day it might catch 90's RAD tooling.
- codingdave 9y agoOne of the reasons it has never taken off is that GUI editors and layout managers that have come out for the web (and there have been a few), have never quite gotten the code right. They would produce a page that looked like the designer... but with terribly written HTML/CSS. So web designers and developers prefer to make their own markup.
- pjmlp 9y agoI seldom recognize pieces of HTML/CSS literature when looking at the developer tools panel, or source code from well known frameworks.
- lkrubner 9y agoThe deeper problem is that the tech industry is slow to get rid of HTML, even though HTML was created to exchange documents, and nowadays we mostly use it as a GUI for network software. See "The Problem With HTML": http://www.smashcompany.com/technology/the-problem-with-html http://www.smashcompany.com/technology/the-problem-with-html
- ahartmetz 9y agoIt used to be conventional wisdom that using HTML as a layout system is wrong, you know. Because it wasn't meant to be one, and text content was supposed to be independent of the medium on which it is viewed. Well, at the time I had my doubts that it was going to work, but it was (and still is) a nice idea.
- TeMPOraL 9y agoThey'd accomplish a lot, but I fear most of it wouldn't take anyway. The problem is the Internet. Or, more precisely, other people. Those systems of old didn't separate between "an user" and "a developer" because they assumed all users are trusted (and responsible people). With the Internet, this assumption immediately becomes false - between people attacking the network and social engineering, it's dangerous to let people have that much control over their environment. Which is something that pisses me off, because I'd love to work on a modern-day version of a Lisp machine, but I understand this can't ever become mainstream (and myself I'd be worried using it to do my banking). Or, as I sometimes phrase it, Star Trek-level tech requires Star Trek-level society.
- TheOtherHobbes 9y agoI suspect there are Laws of Social Computing which guarantee that public networked systems inevitably converge on certain kinds of uses and applications, with certain consistently reinvented “abuses” and failure modes. Networked computing is just a mirror. We seem surprised when some of the things we see it aren’t very nice, but perhaps we shouldn’t be.
- drb91 9y ago> Those systems of old didn't separate between "an user" and "a developer" because they assumed all users are trusted (and responsible people). With the Internet, this assumption immediately becomes false - between people attacking the network and social engineering, it's dangerous to let people have that much control over their environment. More than that: ads. They really did destroy the internet.
- walterbell 9y agoWe now have the HW/SW technology to authenticate and isolate code and individual humans, including the creation of parallel universes (copy-on-write disk and memory for transient VMs that are forked from running code) with optionally persistent side effects. Some of these ideas are present in https://cappsule.github.io/faq/ https://cappsule.github.io/faq/
- dennisdamenace 9y agoWhen trust and finance are not issues, not even considerations.
- mmjaa 9y agoThere really isn't any good reason for OS vendors to not add such a library to their operating systems these days .. except for the fact that they're all asleep at the wheel, having been overwhelmed with the idea of making their OS's browser-centric ..
- justin66 9y agoI'm reading Brian Dear's book now, it's great.
- sien 9y agoHe's on HN https://news.ycombinator.com/user?id=brianstorms https://news.ycombinator.com/user?id=brianstorms Hour Long Podcast with an interview with him here: http://www.internethistorypodcast.com/2017/12/the-forgotten-story-of-plato-with-brian-dear/ http://www.internethistorypodcast.com/2017/12/the-forgotten-...
- kolinko 9y ago+1 on the Internet History Podcast episode. It's awesome (other episodes from IHP as well :) )
- brianstorms 9y agoHi there. Yep I'm here. Ask me anything.
- mncharity 9y ago> the entire PLATO system was designed with social sharing in mind, he says, whereas the modern Internet is more fundamentally suited to fetching websites and documents. > the API was in the operating system and it allowed any app to be social. That was kind of the assumption that the PLATO people had. Hmm, so why didn't the web emphasize social? Ponder... Read-only web. The first web browser(s?) were read-write editors. HTTP GET was paired with PUT. But ramp up happened on read-only browsers (Mosaic, Navigator). User input wasn't possible until ISINDEX and then FORMs. Write didn't become part of the culture. Documents, and separate social. In an ecosystem of ftp, and assorted file formats, and nntp (usenet news), there was a missing integrative piece. HMTL/URLs addressed that. Gopher had similar motivation. HTML was a static document format. But the 'one piece of an ecosystem' model meant social wasn't tightly integrated. If you wanted social, you did news, not WWW. You posted urls. News (distributed social) plateaued, then declined, and the focus of social development shifted to web sites. I was never quite sure why news development stalled. There was a multi-year period, where it was clear what needed to be done to advance (eg voting), but it wasn't happening. One certainly could have built a pervasively social system on top of the web. But it's hard for add-on layers to get traction. Even when they were part of the original vision. For example, X Windows' low-level Xlib, was intended only for the higher-level libraries everyone would then use, but those were slow to materialize, so everyone just stuck with Xlib. Part of why the web worked was its initial simplicity and subsequent feature creeping. The hypertext community was quite miffed that this toy was getting traction, when their various more complex systems were not. But we never got say a news2://... protocol. It seemed dotcom was pulling the oxygen away from a lot of potential infrastructure-ish projects - perhaps that was part of it. Anyway, random musings.
- kolinko 9y agoI'm afraid social methods embeded into HTTP would go the same way LINK/UNLINK (http 1.0), and DELETE,PATCH,OPTIONS,TRACE went - mostly forgotten, and rarely used. Practice has shown that some things are better solved on a higher layer.
- traviscj 9y agoSeems like browser-based PUT is at once "too" generic and simultaneously not self-describing enough for a lot of input. (Should I be allowed to change my wife's facebook details?) The protocol supports rejecting those edits, but what if I want the form itself to change in response to edits I'm proposing? (Greying out the "change password" button, or telling me "You can't change the relationship status of others!") Stepping up from my examples a bit, it seems like you'd need a pretty sophisticated model for ACLs and almost arbitrary client side validations, which we didn't have until javascript.
- brianzelip 9y agoFor a social history of PLATO, see the 50 Years of Public Computing conference that took place at UIUC School of Information (the same year as the Computer History Museum video embedded in the article), http://50years.ischool.illinois.edu/ http://50years.ischool.illinois.edu/.
- bbulkow 9y agoI had my first job programming Plato at UofD. I had my second job building hardware for replacing the old expensive terminals with pcs running the same hardware. A few years later, I came to silicon valley to help the people who put tcp/ip on the Macintosh fight the networking war ( spoiler, tcp/ip won ). Plato had community, and I even bought my first computer from a guy in illinois. There was a form of live chat that even spanned different universities, there were Friday afternoon massively multi player flight simulator battles. in the late 70's. let me give you a quick taste of programming in Tutor. Variables were strings, integers, and shared ( same value for everyone in the program, used for multiuser experiences ). there were 150 integers, called i1, i2, and whatnot. There were no symbolic variables. Since you didn't have to make a network call to communicate between users ( that came with the draconian unix process model ), you could make shared experiences far more easily than today. Ah well.
- brianstorms 9y agoYep me too: first programming job was at PLATO at U of D in 1980.
- brianstorms 9y agoIf you want to find out more about the book, I recommend: http://friendlyorangeglow.com http://friendlyorangeglow.com that is, after you've gotten a copy of the book. Really, everyone in the YC world ought to read this book. It is a completely alien history of computing that has basically nothing to do with Silicon Valley, and in some ways is heresy to Silicon Valley. The PLATO system was built 1000 miles to the east, in Illinois, and had very little (but not zero) cross-fertilization with Silicon Valley thinking. The exception is Xerox PARC, whose people including Kay and Goldberg had regular interactions and trips back and forth with their counterparts at the PLATO lab called CERL at Univ of Illinois. I have a whole chapter on PARC and Kay and how the PLATO project deeply influenced Kay. But seriously, if you have any interest in the untold histories of: • flat-panel gas-plasma display invention • e-learning and online courses (which PLATO was doing, for full credit, as early as mid-60s) • MUDs before MUD-1, including 3D dungeon games • multiplayer graphical games of all sorts • PLATO Notes as a precursor to USENET and Lotus Notes • instant messaging in 1973 • chat rooms in 1973 using Talk-o-matic • screen sharing • phishing, PLATO-style • emoticon long before Internet smileys started • crowdsourced online newspapers • the White House threatening to shut down, in 1973, ARPANET and PLATO, completely, because they had online forums talking about impeachment of Nixon • tons more I'd recommend you read the book. :) Meanwhile, feel free to ask me anything.