Podcasts about history of computing

Smalltalk is one of those programming languages that's lived out of the mainstream, but often referenced as an influence and an important part of programming history. It's the cornerstone of object-oriented programming, it was into message passing before actors were cool, and it blurs the line between operating system, programming language and personal notebook. But what is it?Joining us to discuss it is Juan Vuletich, the creator of one of Smalltalk's latest incarnations, Cuis. In this episode we cover Smalltalk's history, its design ideas, Cuis's unique implementation and what makes this modern implementation something special.Smalltalk is over 50 years old, but its vision of how computing could work has only begun. Let's see if we can mine some ideas from it to take us into the next generation of computing...--The Cuis Smalltalk Book: https://cuis-Smalltalk.github.io/TheCuisBook/Preface.htmlCuis on Github: https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-DevThe Cuis Community: https://cuis.st/communityA Short History of Cuis: https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev/blob/master/Documentation/CuisHistory.mdMonticello VCS: https://wiki.squeak.org/squeak/1287Juan's Music Research: https://www.jvuletich.org/research.htmlBack to the Future - The Story of Squeak (pdf): https://dl.acm.org/doi/pdf/10.1145/263700.263754Kris on Mastodon: http://mastodon.social/@krisajenkinsKris on LinkedIn: https://www.linkedin.com/in/krisjenkins/Kris on Twitter: https://twitter.com/krisajenkins

In this episode, we talk to Mar Hicks, an Associate Professor of Data Science at the University of Virginia and author of Programmed Inequality: How Britain discarded Women Technologists and Lost its Edge in computing. Hicks talks to us about the lessons that the tech industry can learn from histories of computing, for example: how sexism is an integral feature of technological systems and not just a bug that can be extracted from them; how techno-utopianism can stop us from building better technologies; when looking to the past is useful and when it's not helpful; the dangers of the 'move fast and break things' approach where you just build technology just to see what happens; and whether regulatory sandboxes are sufficient in making sure that tech isn't deployed unsafely on an unsuspecting public.

This episode will go into Democrat's gamble on Trump indictment, strikes persist in Germany, and people are fleeing California for obvious reasons. US is helping Costa Rica will cyber attacks, ChatGPT needs to be paused warned some experts like Elon Musk, ChatGPT got its first western ban in Italy following authoritarian nations like North Korea, China, Russia and Iran. Finally, brief history of computing programming is discussing with some female involvement.A. Primary Politics-Timestamp: 6:31https://www.youtube.com/watch?v=r5qOxi_26d8https://www.cnn.com/2023/03/31/investing/stocks-trump-dwac-phunware/index.htmlhttps://www.cnbc.com/2023/03/31/trump-indictment-campaign-uses-facebook-to-fundraise.htmlhttps://www.cnn.com/2023/03/27/business/germany-transport-strikes-intlhttps://nypost.com/2023/04/01/more-than-500000-flee-california-since-2020/B. Mid game-Timestamp: 21:45https://www.wired.com/story/white-house-costa-rica-albania-ransomware-aid/https://www.bbc.com/news/uk-65147841https://www.bbc.com/news/technology-65139406C. Weird Topic Finale (WTF)-Timestamp: 33:22https://www.bricsys.com/en-eu/blog/computer-programing-a-brief-history Hosted on Acast. See acast.com/privacy for more information.

On this episode: Obsolete: History of Computing --- Send in a voice message: https://podcasters.spotify.com/pod/show/man-behind-the-machine/message

Why does the history of computing matter? Joël and Developer at thoughtbot Sara Jackson, ponder this and share some cool stories (and trivia!!) behind the tools we use in the industry. This episode is brought to you by Airbrake (https://airbrake.io/?utm_campaign=Q3_2022%3A%20Bike%20Shed%20Podcast%20Ad&utm_source=Bike%20Shed&utm_medium=website). Visit Frictionless error monitoring and performance insight for your app stack. Sara on Twitter (https://twitter.com/csarajackson) UNIX philosophy (https://en.wikipedia.org/wiki/Unix_philosophy) Hillel Wayne on why we ask linked list questions (https://www.hillelwayne.com/post/linked-lists/) Transcript: JOËL: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Joël Quenneville. And today, I'm joined by fellow thoughtboter, Team Lead, and Developer Sara Jackson. SARA: Hello, happy to be here. JOËL: Together, we're here to share a little bit of what we've learned along the way. So, Sara, what's new in your world? SARA: Well, Joël, you might know that recently our team had a small get-together in Toronto. JOËL: And our team, for those who are not aware, is fully remote distributed across multiple countries. So this was a chance to get together in person. SARA: Yes, correct. This was a chance for those on the Boost team to get together and work together as if we had a physical office. JOËL: Was this your first time meeting some members of the team? SARA: It was my second, for the most part. So I joined thoughtbot, but after thoughtbot had already gotten remote. Fortunately, I was able to meet many other thoughtboters in May at our summit. JOËL: Had you worked at a remote company before coming to thoughtbot? SARA: Yes, I actually started working remotely in 2019, but even then, that wasn't my first time working remotely. I actually had a full year of internship in college that was remote. JOËL: So you were a pro at this long before the pandemic made us all try it out. SARA: I don't know about that, but I've certainly dealt with the idiosyncrasies that come with remote work for longer. JOËL: What do you think are some of the challenges of remote work as opposed to working in person in an office? SARA: I think definitely growing and maintaining a culture. When you're in an office, it's easy to create ad hoc conversations and have events that are small that build on the culture. But when you're remote, it has to be a lot more intentional. JOËL: That definitely rings true for me. One of the things that I really appreciated about in-person office culture was the serendipity that you have those sort of random meetings at the water cooler, those conversations, waiting for coffee with people who are not necessarily on the same team or the same project as you are. SARA: I also really miss being able to have lunch in person with folks where I can casually gripe about an issue I might be having, and almost certainly, someone would have the answer. Now, if I'm having an issue, I have to intentionally seek help. [chuckles] JOËL: One of the funny things that often happened, at least the office where I worked at, was that lunches would often devolve into taxonomy conversations. SARA: I wish I had been there for that. [laughter] JOËL: Well, we do have a taxonomy channel on Slack to somewhat continue that legacy. SARA: Do you have a favorite taxonomy lunch discussion that you recall? JOËL: I definitely got to the point where I hated the classifying a sandwich. That one has been way overdone. SARA: Absolutely. JOËL: There was an interesting one about motorcycles, and mopeds, and bicycles, and e-bikes, and trying to see how do you distinguish one from the other. Is it an electric motor? Is it the power of the engine that you have? Is it the size? SARA: My brain is already turning on those thoughts. I feel like I could get lost down that rabbit hole very easily. [laughter] JOËL: Maybe that should be like a special anniversary episode for The Bike Shed, just one long taxonomy ramble. SARA: Where we talk about bikes. JOËL: Ooh, that's so perfect. I love it. One thing that I really appreciated during our time in Toronto was that we actually got to have lunch in person again. SARA: Yeah, that was so wonderful. Having folks coming together that had maybe never worked together directly on clients just getting to sit down and talk about our day. JOËL: Yeah, and talk about maybe it's work-related, maybe it's not. There's a lot of power to having some amount of deeper interpersonal connection with your co-workers beyond just the we work on a project together. SARA: Yeah, it's like camaraderie beyond the shared mission of the company. It's the shared interpersonal mission, like you say. Did you have any in-person pairing sessions in Toronto? JOËL: I did. It was actually kind of serendipitous. Someone was stuck with a weird failing test because somehow the order factories were getting created in was not behaving in the expected way, and we herd on it, dug into it, found some weird thing with composite primary keys, and solved the issue. SARA: That's wonderful. I love that. I wonder if that interaction would have happened or gotten solved as quickly if we hadn't been in person. JOËL: I don't know about you, but I feel like I sometimes struggle to ask for help or ask for a pair more when I'm online. SARA: Yeah, I agree. It's easier to feel like you're not as big of an impediment when you're in person. You tap someone on the shoulder, "Hey, can you take a look at this?" JOËL: Especially when they're on the same team as you, they're sitting at the next desk over. I don't know; it just felt easier. Even though it's literally one button press to get Tuple to make a call, somehow, I feel like I'm interrupting more. SARA: To combat that, I've been trying to pair more frequently and consistently regardless of if I'm struggling with a problem. JOËL: Has that worked pretty well? SARA: It's been wonderful. The only downside has been pairing fatigue. JOËL: Pairing fatigue is real. SARA: But other than that, problems have gotten solved quickly. We've all learned something for those that I've paired with. It goes faster. JOËL: So it was really great that we had this experience of doing our daily work but co-located in person; we have these experiences of working together. What would you say has been one of the highlights for you of that time? SARA: 100% karaoke. JOËL: [laughs] SARA: Only two folks did not attend. Many of the folks that did attend told me they weren't going to sing, but they were just going to watch. By the end of the night, everyone had sung. We were there for nearly three and a half hours. [laughs] JOËL: It was a good time all around. SARA: I saw a different side to Chad. JOËL: [laughs] SARA: And everyone, honestly. Were there any musical choices that surprised you? JOËL: Not particularly. Karaoke is always fun when you have a group of people that you trust to be a little bit foolish in front of to put yourself out there. I really appreciated the style that we went for, where we have a private room for just the people who were there as opposed to a stage in a bar somewhere. I think that makes it a little bit more accessible to pick up the mic and try to sing a song. SARA: I agree. That style of karaoke is a lot more popular in Asia, having your private room. Sometimes you can find it in major cities. But I also prefer it for that reason. JOËL: One of my highlights of this trip was this very sort of serendipitous moment that happened. Someone was asking a question about the difference between a Mac and Linux operating systems. And then just an impromptu gathering happened. And you pulled up a chair, and you're like, gather around, everyone. In the beginning, there was Multics. It was amazing. SARA: I felt like some kind of historian or librarian coming out from the deep. Let me tell you about this random operating system knowledge that I have. [laughs] JOËL: The ancient lore. SARA: The ancient lore in the year 1969. JOËL: [laughs] And then yeah, we had a conversation walking the history of operating systems, and why we have macOS and Linux, and why they're different, and why Windows is a totally different kind of family there. SARA: Yeah, macOS and Linux are sort of like cousins coming from the same tree. JOËL: Is that because they're both related through Unix? SARA: Yes. Linux and macOS are both built based off of different versions of Unix. Over the years, there's almost like a family tree of these different Nix operating systems as they're called. JOËL: I've sometimes seen asterisk N-I-X. This is what you're referring to as Nix. SARA: Yes, where the asterisk is like the RegEx catch-all. JOËL: So this might be Unix. It might be Linux. It might be... SARA: Minix. JOËL: All of those. SARA: Do you know the origin of the name Unix? JOËL: I do not. SARA: It's kind of a fun trivia piece. So, in the beginning, there was Multics spelled M-U-L-T-I-C-S, standing for the Multiplexed Information and Computing Service. Dennis Ritchie and Ken Thompson of Bell Labs famous for the C programming language... JOËL: You may have heard of it. SARA: You may have heard of it maybe on a different podcast. They were employees at Bell Labs when Multics was being created. They felt that Multics was very bulky and heavy. It was trying to do too many things at once. It did have a few good concepts. So they developed their own smaller Unix originally, Unics, the Uniplexed Information and Computing Service, Uniplexed versus Multiplexed. We do one thing really well. JOËL: And that's the Unix philosophy. SARA: It absolutely is. The Unix philosophy developed out of the creation of Unix and C. Do you know the four main points? JOËL: No, is it small sharp tools? It's the main one I hear. SARA: Yes, that is the kind of quippy version that has come out for sure. JOËL: But there is a formal four-point manifesto. SARA: I believe it's evolved over the years. But it's interesting looking at the Unix philosophy and seeing how relevant it is today in web development. The four points being make each program do one thing well. To this end, don't add features; make a new program. I feel like we have this a lot in encapsulation. JOËL: Hmm, maybe even the open-closed principle. SARA: Absolutely. JOËL: Similar idea. SARA: Another part of the philosophy is expecting output of your program to become input of another program that is yet unknown. The key being don't clutter your output; don't have extraneous text. This feels very similar to how we develop APIs. JOËL: With a focus on composability. SARA: Absolutely. Being able to chain commands together like you see in Ruby all the time. JOËL: I love being able to do this, for example, the enumerable API in Ruby and just being able to chain all these methods together to just very nicely do some pretty big transformations on an array or some other data structure. SARA: 100% agree there. That ability almost certainly came out of following the tenets of this philosophy, maybe not knowingly so but maybe knowingly so. [chuckles] JOËL: So is that three or four? SARA: So that was two. The third being what we know as agile. JOËL: Really? SARA: Yeah, right? The '70s brought us agile. Design and build software to be tried early, and don't hesitate to throw away clumsy parts and rebuild. JOËL: Hmmm. SARA: Even in those days, despite waterfall style still coming on the horizon. It was known for those writing software that it was important to iterate quickly. JOËL: Wow, I would never have known. SARA: It's neat having this history available to us. It's sort of like a lens at where we came from. Another piece of this history that might seem like a more modern concept but was a very big part of the movement in the '70s and the '80s was using tools rather than unskilled help or trying to struggle through something yourself when you're lightening a programming task. We see this all the time at thoughtbot. Folks do this many times there is an issue on a client code. We are able to generalize the solution, extract into a tool that can then be reused. JOËL: So that's the same kind of genesis as a lot of thoughtbot's open-source gems, so I'm thinking of FactoryBot, Clearance, Paperclip, the old-timey file upload gem, Suspenders, the Rails app generator, and the list goes on. SARA: I love that in this last point of the Unix philosophy, they specifically call out that you should create a new tool, even if it means detouring, even if it means throwing the tools out later. JOËL: What impact do you think that has had on the way that tooling in the Unix, or maybe I should say *Nix, ecosystem has developed? SARA: It was a major aspect of the Nix environment community because Unix was available, not free, but very inexpensively to educational institutions. And because of how lightweight it was and its focus on single-use programs, programs that were designed to do one thing, and also the way the shell was allowing you to use commands directly and having it be the same language as the shell scripting language, users, students, amateurs, and I say that in a loving way, were able to create their own tools very quickly. It was almost like a renaissance of Homebrew. JOËL: Not Homebrew as in the macOS package manager. SARA: [laughs] And also not Homebrew as in the alcoholic beverage. JOËL: [laughs] So, this kind of history is fun trivia to know. Is it really something valuable for us as a jobbing developer in 2022? SARA: I would say it's a difficult question. If you are someone that doesn't dive into the why of something, especially when something goes wrong, maybe it wouldn't be important or useful. But what sparked the conversation in Toronto was trying to determine why we as thoughtbot tend to prefer using Macs to develop on versus Linux or Windows. There is a reason, and the reason is in the history. Knowing that can clarify decisions and can give meaning where it feels like an arbitrary decision. JOËL: Right. We're not just picking Macs because they're shiny. SARA: They are certainly shiny. And the first thing I did was to put a matte case on it. JOËL: [laughs] So no shiny in your office. SARA: If there were too many shiny things in my office, boy, I would never get work done. The cats would be all over me. MID-ROLL AD: Debugging errors can be a developer's worst nightmare...but it doesn't have to be. Airbrake is an award-winning error monitoring, performance, and deployment tracking tool created by developers for developers, that can actually help cut your debugging time in half. So why do developers love Airbrake? It has all of the information that web developers need to monitor their application - including error management, performance insights, and deploy tracking! Airbrake's debugging tool catches all of your project errors, intelligently groups them, and points you to the issue in the code so you can quickly fix the bug before customers are impacted. In addition to stellar error monitoring, Airbrake's lightweight APM helps developers to track the performance and availability of their application through metrics like HTTP requests, response times, error occurrences, and user satisfaction. Finally, Airbrake Deploy Tracking helps developers track trends, fix bad deploys, and improve code quality. Since 2008, Airbrake has been a staple in the Ruby community and has grown to cover all major programming languages. Airbrake seamlessly integrates with your favorite apps to include modern features like single sign-on and SDK-based installation. From testing to production, Airbrake notifiers have your back. Your time is valuable, so why waste it combing through logs, waiting for user reports, or retrofitting other tools to monitor your application? You literally have nothing to lose. Head on over to airbrake.io/try/bikeshed to create your FREE developer account today! JOËL: So we've talked a little bit about Unix or *Nix, this evolution of systems. I've also heard the term POSIX thrown around when talking about things that seem to encompass both macOS and Linux. How does that fit into this history? SARA: POSIX is sort of an umbrella of standards around operating systems that was based on Unix and the things that were standard in Unix. It stands for the Portable Operating System Interface. This allowed for compatibility between OSs, very similar to USB being the standard for peripherals. JOËL: So, if I was implementing my own Unix-like operating system in the '80s, I would try to conform to the POSIX standard. SARA: Absolutely. Now, not every Nix operating system is POSIX-compliant, but most are or at least 90% of the way there. JOËL: Are any of the big ones that people tend to think about not compliant? SARA: A major player in the operating system space that is not generally considered POSIX-compliant is Microsoft Windows. JOËL: [laughs] It doesn't even try to be Unix-like, right? It's just its own thing, SARA: It is completely its own thing. I don't think it even has a standard necessarily that it conforms to. JOËL: It is its own standard, its own branch of the family tree. SARA: And that's what happens when your operating system is very proprietary. This has caused folks pain, I'm sure, in the past that may have tried to develop software on their computers using languages that are more readily compatible with POSIX operating systems. JOËL: So would you say that a language like Ruby is more compatible with one of the POSIX-compatible operating systems? SARA: 100% yes. In fact, to even use Ruby as a development tool in Windows, prior to Windows 10, you needed an additional tool. You needed something like Cygwin or MinGW, which were POSIX-compliant programs that it was almost like a shell in your Windows computer that would allow you to run those commands. JOËL: Really? For some reason, I thought that they had some executables that you could run just on Windows by itself. SARA: Now they do, fortunately, to the benefit of Ruby developers everywhere. As of Windows 10, we now have WSL, the Windows Subsystem for Linux that's built-in. You don't have to worry about installing or configuring some third-party software. JOËL: I guess that kind of almost cheats by just having a POSIX system embedded in your non-POSIX system. SARA: It does feel like a cheat, but I think it was born out of demand. The Windows NT kernel, for example, is mostly POSIX-compliant. JOËL: Really? SARA: As a result of it being used primarily for servers. JOËL: So you mentioned the Ruby tends and the Rails ecosystem tends to run better and much more frequently on the various Nix systems. Did it have to be that way? Or is it just kind of an accident of history that we happen to end up with Ruby and Rails in this ecosystem, but just as easily, it could have evolved in the Windows world? SARA: I think it is an amalgam of things. For example, Unix and Nix operating systems being developed earlier, being widely spread due to being license-free oftentimes, and being widely used in the education space. Also, because it is so lightweight, it is the operating system of choice. For most servers in the world, they're running some form of Unix, Linux, or macOS. JOËL: I don't think I've ever seen a server that runs macOS; exclusively seen it on dev machines. SARA: If you go to an animation company, they have server farms of macOS machines because they're really good at rendering. This might not be the case anymore, but it was at one point. JOËL: That's a whole other world that I've not interacted with a whole lot. SARA: [chuckles] JOËL: It's a fun intersection between software, and design, and storytelling. That is an important part for the software field. SARA: Yeah, it's definitely an aspect that deserves its own deep dive of sorts. If you have a server that's running a Windows-based operating system like NT and you have a website or a program that's designed to be served under a Unix-based server, it can easily be hosted on the Windows server; it's not an issue. The reverse is not true. JOËL: Oh. SARA: And this is why programming on a Nix system is the better choice. JOËL: It's more broadly compatible. SARA: Absolutely. Significantly more compatible with more things. JOËL: So today, when I develop, a lot of the tooling that I use is open source. The open-source movement has created a lot of the languages that we know and love, including Ruby, including Rails. Do you think there's some connection between a lot of that tooling being open source and maybe some of the Unix family of operating systems and movements that came out of that branch of the operating system family tree? SARA: I think that there is a lot of tie-in with today's open-source culture and the computing history that we've been talking about, for example, people finding something that they dislike about the tools that are available and then rolling their own. That's what Ken Thompson and Dennis Ritchie did. Unix was not an official Bell development. It was a side project for them. JOËL: I love that. SARA: You see this happen a lot in the software world where a program gets shared widely, and due to this, it gains traction and gains buy-in from the community. If your software is easily accessible to students, folks that are learning, and breaking things, and rebuilding, and trying, and inventing, it's going to persist. And we saw that with Unix. JOËL: I feel like this background on where a lot of these operating systems came but then also the ecosystems, the values that evolved with them has given me a deeper appreciation of the tooling, the systems that we work with today. Are there any other advantages, do you think, to trying to learn a little bit of computing history? SARA: I think the main benefit that I mentioned before of if you're a person that wants to know why, then there is a great benefit in knowing some of these details. That being said, you don't need to deep dive or read multiple books or write papers on it. You can get enough information from reading or skimming some Wikipedia pages. But it's interesting to know where we came from and how it still affects us today. Ruby was written in C, for example. Unix was written in C as well, originally Assembly Language, but it got rewritten in C. And understanding the underlying tooling that goes into that that when things go wrong, you know where to look. JOËL: I guess that that is the next question is where do you look if you're kind of interested? Is Wikipedia good enough? You just sort of look up operating system, and it tells you where to go? Or do you have other sources you like to search for or start pulling at those threads to understand history? SARA: That's a great question. And Wikipedia is a wonderful starting point for sure. It has a lot of the abbreviated history and links to better references. I don't have them off the top of my head. So I will find them for you for the show notes. But there are some old esoteric websites with some of this history more thoroughly documented by the people that lived it. JOËL: I feel like those websites always end up being in HTML 2; your very basic text, horizontal rules, no CSS. SARA: Mm-hmm. And those are the sites that have many wonderful kernels of knowledge. JOËL: Uh-huh! Great pun. SARA: [chuckles] Thank you. JOËL: Do you read any content by Hillel Wayne? SARA: I have not. JOËL: So Hillel produces a lot of deep dives into computing history, oftentimes trying to answer very particular questions such as when and why did we start using reversing a linked list as the canonical interview question? And there are often urban legends around like, oh, it's because of this. And then Hillel will do some research and go through actual archives of messages on message boards or...what is that protocol? SARA: BBS. JOËL: Yes. And then find the real answer, like, do actual historical methodology, and I love that. SARA: I had not heard of this before. I don't know how. And that is all I'm going to be doing this weekend is reading these. That kind of history speaks to my heart. I have a random fun fact along those lines that I wanted to bring to the show, which was that the echo command that we know and love in the terminal was first introduced by the Multics operating system. JOËL: Wow. So that's like the most common piece of Multics that as an everyday user of a modern operating system that we would still touch a little bit of that history every day when we work. SARA: Yeah, it's one of those things that we don't think about too much. Where did it come from? How long has it been around? I'm sure the implementation today is very different. But it's like etymology, and like taxonomy, pulling those threads. JOËL: Two fantastic topics. On that wonderful little nugget of knowledge, let's wrap up. Sara, where can people find you online? SARA: You can find me on Twitter at @csarajackson. JOËL: And we will include a link to that in the show notes. SARA: Thank you so much for having me on the show and letting me nerd out about operating system history. JOËL: It's been a pleasure. The show notes for this episode can be found at bikeshed.fm. This show is produced and edited by Mandy Moore. If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review on iTunes. It really helps other folks find the show. If you have any feedback, you can reach us at @_bikeshed or reach me @joelquen on Twitter or at hosts@bikeshed.fm via email. Thank you so much for listening to The Bike Shed, and we'll see you next week. Byeeeeee!!!! ANNOUNCER: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

In this episode, Columbia literature curator Lina Moe sits down with historian and curator of NYU's AI Now Institute and author of A People's History of Computing in the United States, Joy Lisi Rankin. Lina and Joy discuss urgent questions about the social history of computing; the ethical dilemmas posed by the power of tech industry giants today; and how race, class, and gender factor into online culture. Lina and Joy also speculate on the paths not taken in computing. Instead of understanding computers as commodities for purchase, for example, computers could have been considered necessary public goods, similar to utilities. Joy provides fascinating archival stories that shift the paradigms of computer history, like how instant messaging was created as an educational tool decades before AOL popularized it--or how a Minnesota librarian wrote the early software for what became Apple's music library, but was never paid for it. Overdue Conversations is a podcast about the ways archives inform our discussions around history, literature, and politics. From digital publishing to reparative justice, climate change to public health, this series of overdue conversations takes archival documents out of the stacks and into the public forum to consider how collecting practices, selective reading, and erasure of past knowledge informs and distorts contemporary debates. Music is by Poddington Bear via the Free Music Archive used under Creative Commons license. Overdue tile design by Amy Howden-Chapman. Researched and produced by Lina Moe and Anirbaan Banerjee with assistance from Amanda Martin-Hardin.

The second season of Cut Pathways, the oral history podcast from the Carnegie Mellon University Oral History Program, dives into the influential history of computer science at CMU. In a six-episode series, titled “The Wild West of Computing,” hosts Katherine Barbera and David Bernabo along with guests historian Andrew Meade McGee and Curator of Special Collections Sam Lemley show how the culture surrounding computer science significantly altered the reputation of the school from 1956 to 1987.    In this episode, we get a byte-sized history of computing and learn about the very early days of computer science at CMU.

Greetings, Comrades!Today, we're looking at the weird and interesting history of computers and cybernetics as it were in the Soviet Union. Because now and then, I'd like to cover topics that are actually, you know, NOT terribly depressing. Also, don't forget to check out Advent of Computing podcast, and enjoy!Happiness is Mandatory!Support this show http://supporter.acast.com/theeasternborder. See acast.com/privacy for privacy and opt-out information.

When was the first computer

I want to share my brand new project:HEALTH SECRETS: THE 10 MINUTE WEB CLASS. Here is what you will learn inside the class.Secret 1: What did 46 medical doctors and 4 medical boards discover in 2016 that became the new # 1 influencer over your physical health? (I'll bet you have never heard of it)​Secret 2: A brand new education framework being shared with over 1 million students worldwide that will bring you a lifetime of physical health. (I'll bet you have never heard this one either)​Secret 3: A new technology that will allow you to auto-track secret # 1 as soon as the 10-minute web class is over. It has 20 million users worldwide and backed by one of the world's major medical studies into physical health. I will give it to you FREE at the end of this class!IF YOU WANT TO WATCH HEALTH SECRETS: THE 10 MINUTE WEB CLASS, then let me know by clicking this link.https://forms.gle/atFEYuxfEBUSjpU78Today's episode.So who is the most famous person in commuting history? And the next question is how did I get to spend three hours with this person almost one on one, way back in the year 2000. Today's episode explores the answer to that question and how it's linked directly to the concept of the New Science of Physical Health and drawing you into that world - and the impact it will have on improving your physical health destiny.Who do you think is the most famous person in computing history. See inside today's episode if it matches mine and discover exactly how I spent 3 hours helping them on September 15th, 2020 in Sydney Australia.

We live in a world built by our collective ingenuity and imagination. We see further and more than our predecessors, not because of keener vision or greater heights but because we are standing on the shoulders of giants that came before us. The Japanese word "sensei" literally means the person who came before. Do you remember the first time you touch the computer keyboard? Do you remember the typewriter clanging sound? Do you remember your first HTML rendered on the world wide web or your first "hello world" application? Maybe you were a gamer, and you blew the cartridges on your family computer? No doubt, your first lines of code relies on the combined outcomes of thousands of years of accumulated knowledge and wisdom. Today, we will navigate through history to discover how our ancestors made knowledge out of information. We'll talk about the technologies that have marked contemporary and modern history. Then we'll go back to modern times to talk about the first web server, virtualization, cloud computing, Docker and Kubernetes. This is the tale of computing, in which humans are heroes, and their greatest weapon is the imagination. --- Send in a voice message: https://anchor.fm/thedevopsfauncast/message Support this podcast: https://anchor.fm/thedevopsfauncast/support

In this episode we wrap up the greatest achievements and challenges in the computing era of the 1960's.  We learn about Howard Tindall, and how MIT became a dominant force in Apollo.  We also learn about Core Rope Memory and how Seamstresses helped program Apollo capsules.  This is the last episode of Season 1, it's time to go offline and research how a new era of computing arrives: Microcomputing.  

The early 1960's were full of gigantic leaps in computing technology, and a lot of it was used in NASA to get astronauts into space!  We see the first use of the word Mainframes, and see how Neil Armstrong used a new invention called "secondary storage" to try to save his own life!

We go knee-deep into available computing technology in the late 1950's and what it was used for: Missles and Satellites.  We see the creation of the NASA RTCC in a muddy field and revisit what IBM is up to.

In this episode, we learn about what company Walt Disney had the pleasure of being the first customer of, we learn about the Traitorous 8, a sweet Missouri man and a PhD grad from Stanford who had the exact same idea at the same time, and how NOT to run an office. We also uneventfully visit the man who coined the phrase "Silicon Valley" who himself earned the nickname "the Hitler of the 1980's" later in life. We have our first visit with a reoccurring name on this podcast, and it's a man we will grow to know as the Mayor.

Episode 8 covers the amazing achievements of women in early computing, including an excellent mathematician who makes sense of programming languages, and a bombshell actress who invented something that makes it possible for us to use computers wirelessly.

In this episode, we get a look at the first commercially available computer: UNIVAC.  We also touch upon the first vacuum tube-free computer and learn the frightening, yet triumphant story behind the inventor of the circuit board.

In the 1930's, we continued experimenting with magnets and electricity, creating places to save data for the first time, including a Memory Drum and tape (thanks to BASF).  Alan Turing puts human learning to a machine for the first time, and two computers across the northeast do math together. 

In this episode, I set out to explain the creation of the teletype, because it happens right around this time, in the 1920’s.  It’s a huge development in the way devices talk to each other, and a jump toward the modem and networking. 

This episode looks at some really interesting inventions with the Bulb and Electricity that played a major role in the development of the electronic computer.  This includes vacuum tubes and Cathode Ray Tubes (CRT's).

In this episode, we solve the problem of calculating from inaccurate tables, learn about NYU Art Professor and inventor of the first electrical language: Samuel Morse, and we discover how the Tabulating Machine company got its start and made one man very rich (and the census a lot easier).  Tune in!

A couple of things we’ll cover in this first episode is who I am and what I’m doing with this Podcast.  I thought it would be a good idea to tell you what I have to do with Computing and technology before I take you on this huge road trip through the entire history of computing.  We’ve got a lot to talk about, and I’ve mapped it out in 18 episodes so far, but I have a feeling we’ll go a little beyond that.  I’m looking forward to this next year or so together with you, while we take this journey.

In this first episode, I go over the beginning of computing: why did we start this thing in the first place?  We review the Abacus, the plague, and the loom, and see why those factored into the device you're reading this on. 

Humans have always looked at how to do things easier. Whether its to use an Abacus to quickly count inventory, automate accounting math using a machine, or quickly calculating ballistics trajectories using wires and Ferrite rings. Now, most of us use hand-held computers to simplify our lives, and the functions are doing just that! But, how did we get here? And who is responsible for all these great ideas? We'll explore this, looking into the origins of some of the most amazing devices and the people who came up with the ideas that led to them. Tune in for the science, thinking (and sometimes controversy) behind the History of Computing! Available everywhere on November 1st!

In Falken's Maze, technologist and former professor Jason Thomas explores the intersection of technology, history, and culture. Created for listeners nostalgic for the 80s but who also want to understand the complexities of today, our show demystifies the world's most compelling technologies and events through 80's movies, music, and television. This is where history, tech, and retro pop collide. If you enjoy the show, tell a friend, leave a review, click some stars!! Find us online at www.falkenspodcast.com. References: Binary and Data (Khan Academy) Jaime Escalante Biography Jaime Escalante, Inspiration for a Movie, Dies at 79 Stand and Deliver Clip Music: CBS Special Presentation Intro Street Dancing by Timecrawler 82 is Licensed under a Creative Commons Attribution (4.0) International license Paint The Sky by Dysfunction_AL (c) copyright 2015 Licensed under a Creative Commons Attribution (3.0) license. Right About Time Open Music Revolution Innovation Open Music Revolution

In Falken's Maze, technologist and former professor Jason Thomas explores the intersection of technology, history, and culture. Created for listeners nostalgic for the 80s but who also want to understand the complexities of today, our show demystifies the world's most compelling technologies and events through 80's movies, music, and television. This is where history, tech, and retro pop collide. If you enjoy the show, tell a friend, leave a review, click some stars!! Find us online at www.falkenspodcast.com. References: WarGames Hacking Clip AOL Dialup Modem Sound The Most Human Human: What Artificial Intelligence Teaches Us About Being Alive by Brian Christian Betty Shannon, Unsung Mathematical Genius by Jimmy Soni and Rob Goodman A Mathematical Theory of Information by C.E. Shannon How Bits and Bytes Work by Marshall Brain Binary and Data (Khan Academy) Music: CBS Special Presentation Intro Street Dancing by Timecrawler 82 is Licensed under a Creative Commons Attribution (4.0) International license Paint The Sky by Dysfunction_AL (c) copyright 2015 Licensed under a Creative Commons Attribution (3.0) license. Right About Time Open Music Revolution Innovation Open Music Revolution

We know, perhaps too well, the innovation-centric history of personal computing. Yet, computer users were not necessarily microelectronics consumers from the get-go; rather, earlier efforts to expand mainframe computing as a public utility made elite information technology accessible to a wide audience. In A People's History of Computing in the United States (Harvard University Press, 2018), Joy Lisi Rankin seeks to restore this broader perspective by situating the history of educational computing within the arc of U.S. social politics in the 1960s and 1970s. The result is a new perspective that challenges the business-dominated historiography of computing by explaining the convergence between the technical and social through efforts that began locally. As these projects expanded in scope, their advocates articulated a vision of "computing citizenship" throughout the rise of what we now call the "information age." Through a series of cases, beginning with timesharing at Dartmouth and the development of the BASIC programming language, through efforts by the state of Minnesota to make the fruits of its high-tech industry available to all, and ending with perhaps the most successful early computing network, the University of Illinois's PLATO project, Rankin makes a compelling case for a social history of computing. Historians of technology, education, and U.S. social history will all find a new resource—and perhaps a new timeline—in this beautifully researched and written book. Mikey McGovern is a PhD candidate in Princeton University's Program in the History of Science. He works on computing, quantification, communication, and governance in modern America. Learn more about your ad choices. Visit megaphone.fm/adchoices

We know, perhaps too well, the innovation-centric history of personal computing. Yet, computer users were not necessarily microelectronics consumers from the get-go; rather, earlier efforts to expand mainframe computing as a public utility made elite information technology accessible to a wide audience. In A People's History of Computing in the United States (Harvard University Press, 2018), Joy Lisi Rankin seeks to restore this broader perspective by situating the history of educational computing within the arc of U.S. social politics in the 1960s and 1970s. The result is a new perspective that challenges the business-dominated historiography of computing by explaining the convergence between the technical and social through efforts that began locally. As these projects expanded in scope, their advocates articulated a vision of "computing citizenship" throughout the rise of what we now call the "information age." Through a series of cases, beginning with timesharing at Dartmouth and the development of the BASIC programming language, through efforts by the state of Minnesota to make the fruits of its high-tech industry available to all, and ending with perhaps the most successful early computing network, the University of Illinois's PLATO project, Rankin makes a compelling case for a social history of computing. Historians of technology, education, and U.S. social history will all find a new resource—and perhaps a new timeline—in this beautifully researched and written book. Mikey McGovern is a PhD candidate in Princeton University’s Program in the History of Science. He works on computing, quantification, communication, and governance in modern America. Learn more about your ad choices. Visit megaphone.fm/adchoices

We know, perhaps too well, the innovation-centric history of personal computing. Yet, computer users were not necessarily microelectronics consumers from the get-go; rather, earlier efforts to expand mainframe computing as a public utility made elite information technology accessible to a wide audience. In A People's History of Computing in the United States (Harvard University Press, 2018), Joy Lisi Rankin seeks to restore this broader perspective by situating the history of educational computing within the arc of U.S. social politics in the 1960s and 1970s. The result is a new perspective that challenges the business-dominated historiography of computing by explaining the convergence between the technical and social through efforts that began locally. As these projects expanded in scope, their advocates articulated a vision of "computing citizenship" throughout the rise of what we now call the "information age." Through a series of cases, beginning with timesharing at Dartmouth and the development of the BASIC programming language, through efforts by the state of Minnesota to make the fruits of its high-tech industry available to all, and ending with perhaps the most successful early computing network, the University of Illinois's PLATO project, Rankin makes a compelling case for a social history of computing. Historians of technology, education, and U.S. social history will all find a new resource—and perhaps a new timeline—in this beautifully researched and written book. Mikey McGovern is a PhD candidate in Princeton University’s Program in the History of Science. He works on computing, quantification, communication, and governance in modern America. Learn more about your ad choices. Visit megaphone.fm/adchoices

We know, perhaps too well, the innovation-centric history of personal computing. Yet, computer users were not necessarily microelectronics consumers from the get-go; rather, earlier efforts to expand mainframe computing as a public utility made elite information technology accessible to a wide audience. In A People's History of Computing in the United States (Harvard University Press, 2018), Joy Lisi Rankin seeks to restore this broader perspective by situating the history of educational computing within the arc of U.S. social politics in the 1960s and 1970s. The result is a new perspective that challenges the business-dominated historiography of computing by explaining the convergence between the technical and social through efforts that began locally. As these projects expanded in scope, their advocates articulated a vision of "computing citizenship" throughout the rise of what we now call the "information age." Through a series of cases, beginning with timesharing at Dartmouth and the development of the BASIC programming language, through efforts by the state of Minnesota to make the fruits of its high-tech industry available to all, and ending with perhaps the most successful early computing network, the University of Illinois's PLATO project, Rankin makes a compelling case for a social history of computing. Historians of technology, education, and U.S. social history will all find a new resource—and perhaps a new timeline—in this beautifully researched and written book. Mikey McGovern is a PhD candidate in Princeton University’s Program in the History of Science. He works on computing, quantification, communication, and governance in modern America. Learn more about your ad choices. Visit megaphone.fm/adchoices

We know, perhaps too well, the innovation-centric history of personal computing. Yet, computer users were not necessarily microelectronics consumers from the get-go; rather, earlier efforts to expand mainframe computing as a public utility made elite information technology accessible to a wide audience. In A People's History of Computing in the United States (Harvard University Press, 2018), Joy Lisi Rankin seeks to restore this broader perspective by situating the history of educational computing within the arc of U.S. social politics in the 1960s and 1970s. The result is a new perspective that challenges the business-dominated historiography of computing by explaining the convergence between the technical and social through efforts that began locally. As these projects expanded in scope, their advocates articulated a vision of "computing citizenship" throughout the rise of what we now call the "information age." Through a series of cases, beginning with timesharing at Dartmouth and the development of the BASIC programming language, through efforts by the state of Minnesota to make the fruits of its high-tech industry available to all, and ending with perhaps the most successful early computing network, the University of Illinois's PLATO project, Rankin makes a compelling case for a social history of computing. Historians of technology, education, and U.S. social history will all find a new resource—and perhaps a new timeline—in this beautifully researched and written book. Mikey McGovern is a PhD candidate in Princeton University’s Program in the History of Science. He works on computing, quantification, communication, and governance in modern America. Learn more about your ad choices. Visit megaphone.fm/adchoices

We know, perhaps too well, the innovation-centric history of personal computing. Yet, computer users were not necessarily microelectronics consumers from the get-go; rather, earlier efforts to expand mainframe computing as a public utility made elite information technology accessible to a wide audience. In A People's History of Computing in the United States (Harvard University Press, 2018), Joy Lisi Rankin seeks to restore this broader perspective by situating the history of educational computing within the arc of U.S. social politics in the 1960s and 1970s. The result is a new perspective that challenges the business-dominated historiography of computing by explaining the convergence between the technical and social through efforts that began locally. As these projects expanded in scope, their advocates articulated a vision of "computing citizenship" throughout the rise of what we now call the "information age." Through a series of cases, beginning with timesharing at Dartmouth and the development of the BASIC programming language, through efforts by the state of Minnesota to make the fruits of its high-tech industry available to all, and ending with perhaps the most successful early computing network, the University of Illinois's PLATO project, Rankin makes a compelling case for a social history of computing. Historians of technology, education, and U.S. social history will all find a new resource—and perhaps a new timeline—in this beautifully researched and written book. Mikey McGovern is a PhD candidate in Princeton University’s Program in the History of Science. He works on computing, quantification, communication, and governance in modern America. Learn more about your ad choices. Visit megaphone.fm/adchoices

We know, perhaps too well, the innovation-centric history of personal computing. Yet, computer users were not necessarily microelectronics consumers from the get-go; rather, earlier efforts to expand mainframe computing as a public utility made elite information technology accessible to a wide audience. In A People's History of Computing in the United States (Harvard University Press, 2018), Joy Lisi Rankin seeks to restore this broader perspective by situating the history of educational computing within the arc of U.S. social politics in the 1960s and 1970s. The result is a new perspective that challenges the business-dominated historiography of computing by explaining the convergence between the technical and social through efforts that began locally. As these projects expanded in scope, their advocates articulated a vision of "computing citizenship" throughout the rise of what we now call the "information age." Through a series of cases, beginning with timesharing at Dartmouth and the development of the BASIC programming language, through efforts by the state of Minnesota to make the fruits of its high-tech industry available to all, and ending with perhaps the most successful early computing network, the University of Illinois's PLATO project, Rankin makes a compelling case for a social history of computing. Historians of technology, education, and U.S. social history will all find a new resource—and perhaps a new timeline—in this beautifully researched and written book. Mikey McGovern is a PhD candidate in Princeton University’s Program in the History of Science. He works on computing, quantification, communication, and governance in modern America. Learn more about your ad choices. Visit megaphone.fm/adchoices

We know, perhaps too well, the innovation-centric history of personal computing. Yet, computer users were not necessarily microelectronics consumers from the get-go; rather, earlier efforts to expand mainframe computing as a public utility made elite information technology accessible to a wide audience. In A People's History of Computing in the United States (Harvard University Press, 2018), Joy Lisi Rankin seeks to restore this broader perspective by situating the history of educational computing within the arc of U.S. social politics in the 1960s and 1970s. The result is a new perspective that challenges the business-dominated historiography of computing by explaining the convergence between the technical and social through efforts that began locally. As these projects expanded in scope, their advocates articulated a vision of "computing citizenship" throughout the rise of what we now call the "information age." Through a series of cases, beginning with timesharing at Dartmouth and the development of the BASIC programming language, through efforts by the state of Minnesota to make the fruits of its high-tech industry available to all, and ending with perhaps the most successful early computing network, the University of Illinois's PLATO project, Rankin makes a compelling case for a social history of computing. Historians of technology, education, and U.S. social history will all find a new resource—and perhaps a new timeline—in this beautifully researched and written book. Mikey McGovern is a PhD candidate in Princeton University’s Program in the History of Science. He works on computing, quantification, communication, and governance in modern America. Learn more about your ad choices. Visit megaphone.fm/adchoices

Intro/Outro: AllIknow (Hip Hop) by Makaih Beats is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 License.

“The history of computing: what can it offer to those who are inventing the future of computing?” foi a palestra a cargo de Paul Ceruzzi. Paul Ceruzzi é curador de eletrónica aeroespacial e de computação do Departamento de História Espacial do Museu Nacional do Ar e do Espaço, Smithsonian Institution, em Washington, DC. Antes de ingressar no Smithsonian, Paul Ceruzzi lecionou história na Clemson University, na Carolina do Sul. (Esta é a segunda parte da talk do investigador Paul Ceruzzi.)

“The history of computing: what can it offer to those who are inventing the future of computing?” foi a palestra a cargo de Paul Ceruzzi. Paul Ceruzzi é curador de eletrónica aeroespacial e de computação do Departamento de História Espacial do Museu Nacional do Ar e do Espaço, Smithsonian Institution, em Washington, DC. Antes de ingressar no Smithsonian, Paul Ceruzzi lecionou história na Clemson University, na Carolina do Sul. (Esta é a segunda parte da talk do investigador Paul Ceruzzi.)

In the second half of "History of Computing", Corey and Geoff discuss the wild evolution of programming languages. Why do we have so many options for languages in the field of software and when would we choose one over another? What computational changes and industry demands cause the growth of new languages?

In this first part of "History of Computing", Corey and Geoff go over the brief history of computing from early mechanical sketches and "programs" to electrical machinery and the development of the modern system. How did some drama in census bureau during the 1880s lead to IBM and expedite computational technology? If you check out Episode 2, "Understanding Data", it may give a greater appreciation for some of the content covered here!

Jim and Devin walk through the list of technology companies where Jim has worked over the years. We talk about the lessons learned as they apply to PE-owned tech companies in the middle market. We cover decades of computing from Digital Equipment Corporation to Oracle and beyond. Bonus content includes a Rupert Pupkin shoutout and a Regis Philbin impression.

In this panel discussion, three people who knew Christopher Strachey in different contexts talk about their memories of him. Michael Jackson discusses being taught by Strachey as a boy at Harrow, David Hartley talks about work with Strachey on the programming language CPL, and Roger Penrose remembers working with Strachey at the National Research Development Corporation and introducing him to lambda calculus.

The logician Dana Scott played a crucial part in the story of denotational semantics, working for a term with Christopher Strachey in Autumn 1969, when he created a mathematical model for the foundation of the method. In this talk, Dana discusses this period as well as reminiscing about his life and career up to that point.

Philip reviews Christopher Strachey’s influence on modern-day functional programming languages.

During Peter’s DPhil studies, supervised by Christopher Strachey, he developed a prototype of a system for executing programs based on their denotational semantics. It involved partial evaluation of lambda-notation, implemented using Wadsworth's call-by-need algorithm. He continued the development of the system as a postdoc at Oxford, and subsequently at Aarhus, Denmark. The system was called SIS: Semantics Implementation System. In this talk, Peter recalls Strachey's influence on his research and on the development of SIS, starting from Strachey’s summer school course on symbolic computation at the PRG in 1969.

A historian’s perspective on the earlier years of Christopher Strachey’s life. The talk covers his familial connections, his early career as a school master, and his first computing projects.

Christopher Strachey’s right-hand man at Oxford talks about Strachey’s time as the head of the Programming Research Group (PRG). The talk covers the foundation of the PRG and the research performed at the (PRG), with an emphasis on the equal importance of theoretical and practical work.

Chrisopher Strachey was the most significant contributor to the design and implementation of the programming language CPL. At the time there was little understanding of the complexities of computer language design and how type systems could cope with lists and the kinds of structures needed to represent, for instance, parse trees. The CPL project cannot be regarded as being successful since it did not result in a usable CPL compiler. The reasons being that the language became too large and complicated, there were insufficient people to implement the compiler and, in the middle of the three year project, all work had to be transferred from Edsac 2 to Titan, a newly designed version of the Ferranti Atlas computer which as yet had no operating system. Even so, we can be proud of the work that went into CPL and its influence on the design of many later languages.

Christopher Strachey believed that the gap between theory and practice was impeding the development of computing science. In Robert’s talk, he considers how the work he did with Strachey on the essay that ultimately became their book tried to narrow the gap, by formalising, and reasoning about, the implementation concepts for programming languages. A particular focus will be the proof techniques for imperative programs that use storage, which were implicit, but not very easy to discern, in the book.

The History of computing has fit an extraordinary amount into a very short time. Professor Martyn Thomas takes us through it here: http://www.gresham.ac.uk/lectures-and-events/a-very-brief-history-of-computing-1948-2015The world's first modern computer, in Manchester in 1948, was followed remarkably swiftly by the first business software, but by 1968 software was in crisis and NATO called a conference. The problems were diagnosed; solutions were proposed - and largely ignored. A second Software Crisis was announced in the early 1980's and again the effective solutions were considered impractical and the practical solutions were largely ineffective. Meanwhile as Moore's Law predicted, hardware costs continued to fall exponentially, making software systems ubiquitous and leading to a third software crisis, this time of cybersecurity.The transcript and downloadable versions of the lecture are available from the Gresham College website: http://www.gresham.ac.uk/lectures-and-events/a-very-brief-history-of-computing-1948-2015Gresham College has been giving free public lectures since 1597. This tradition continues today with all of our five or so public lectures a week being made available for free download from our website. There are currently over 1,800 lectures free to access or download from the website.Website: http://www.gresham.ac.ukTwitter: http://twitter.com/GreshamCollegeFacebook: https://www.facebook.com/greshamcollegeInstagram: http://www.instagram.com/greshamcollege 

Author Grady Booch provides an audio recording of his On Computing column, in which he discusses how although we live in a world of unprecedented complexity and astonishing possibility, we should never forget our past, for those who came before us in computing enabled those possibilities. From IEEE Software's January/February 2016 issue: http://www.computer.org/csdl/mags/so/2016/01/index.html. Visit IEEE Software: http://www.computer.org/software.

A discussion of the core concepts of modern computing and their basis in history.Dr Doron Swade offers a new analysis of the history of computing, suggesting that instead of a linear progression from one phase to the next, it is better understood as a series of separate computational functions diverging and converging.Dr Swade goes beyond the analysis of the history of computing as moving from the Mechanical to the Electromechanical and then to the Electronic phase. Instead he argues that the history of computing is better understood as the diverging and merging of a series of streams which represent very separate computational functions or paradigms: Calculation, Automatic Computation, Information Management, Communication and the Electronic Information Age.This is the 2013 Gresham-BSHM lecture, tracing the origins of the core concepts of modern computing.The transcript and downloadable versions of the lecture are available from the Gresham College website: http://www.gresham.ac.uk/lectures-and-events/the-grand-narrative-of-the-history-of-computingGresham College has been giving free public lectures since 1597. This tradition continues today with all of our five or so public lectures a week being made available for free download from our website. There are currently over 1,500 lectures free to access or download from the website.Website: http://www.gresham.ac.ukTwitter: http://twitter.com/GreshamCollegeFacebook: https://www.facebook.com/greshamcollege

Only looking at coloured imagery leads to new viewpoints and narratives for otherwise well-known histories, and the history of computing is no exception.Martin Campbell-Kelly reconstructs a history of computing from surprisingly rarely-seen colour images.This is a part of the 2013 Gresham College / British Society of the History of Mathematics conference.The transcript and downloadable versions of the lecture are available from the Gresham College website: http://www.gresham.ac.uk/lectures-and-events/the-history-of-computing-in-colourGresham College has been giving free public lectures since 1597. This tradition continues today with all of our five or so public lectures a week being made available for free download from our website. There are currently over 1,500 lectures free to access or download from the website.Website: http://www.gresham.ac.ukTwitter: http://twitter.com/GreshamCollegeFacebook: https://www.facebook.com/greshamcollege

Created in partnership with the National Museum of Computing at Bletchley Park and E2BN. Resource available from Autumn 2013. www.hoc.lgfl.net

  Add mixed retro.  Stir and Serve.Welcome to Show 055!  This week's Topic: Retro Mix (A Variety Episode)! Topics and links discussed in the podcast... Check out A2Central for info on the recent KansasFest 2006, and all your Apple II needs!Also check out the official KFest site - it's never too early to plan for 2007...Here's a presentation on SymbOS by the creator (Google Video - note that the intro is in Spanish, but the presentation is in English).The History Of Computing project - from 30,000 years ago to today, computing is exciting!ADTPro - the latest incarnation of Apple Disk Transfer - check it out today on their SourceForge project page... Be sure to send any comments, questions or feedback to retrobits@gmail.com. For online discussions on Retrobits Podcast topics, check out the Retrobits Podcast forum on the PETSCII Forums page! Our Theme Song is "Sweet" from the "Re-Think" album by Galigan. Thanks for listening! - Earl