home.social

#historyofcomputing — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #historyofcomputing, aggregated by home.social.

  1. Tom’s Hardware: Original Apollo 11 code open-sourced by NASA — original Command Module and Lunar Module code repos are now public domain resources. “The historic computer software code that took Apollo 11 to the moon has been open-sourced and is available for anyone to read, download, and tinker with. NASA’s Chris Garry made the code available on GitHub as public domain. The published […]

    https://rbfirehose.com/2026/04/17/toms-hardware-original-apollo-11-code-open-sourced-by-nasa-original-command-module-and-lunar-module-code-repos-are-now-public-domain-resources/
  2. Tom’s Hardware: Original Apollo 11 code open-sourced by NASA — original Command Module and Lunar Module code repos are now public domain resources. “The historic computer software code that took Apollo 11 to the moon has been open-sourced and is available for anyone to read, download, and tinker with. NASA’s Chris Garry made the code available on GitHub as public domain. The published […]

    https://rbfirehose.com/2026/04/17/toms-hardware-original-apollo-11-code-open-sourced-by-nasa-original-command-module-and-lunar-module-code-repos-are-now-public-domain-resources/
  3. Tom’s Hardware: Original Apollo 11 code open-sourced by NASA — original Command Module and Lunar Module code repos are now public domain resources. “The historic computer software code that took Apollo 11 to the moon has been open-sourced and is available for anyone to read, download, and tinker with. NASA’s Chris Garry made the code available on GitHub as public domain. The published […]

    https://rbfirehose.com/2026/04/17/toms-hardware-original-apollo-11-code-open-sourced-by-nasa-original-command-module-and-lunar-module-code-repos-are-now-public-domain-resources/
  4. Tom’s Hardware: Original Apollo 11 code open-sourced by NASA — original Command Module and Lunar Module code repos are now public domain resources. “The historic computer software code that took Apollo 11 to the moon has been open-sourced and is available for anyone to read, download, and tinker with. NASA’s Chris Garry made the code available on GitHub as public domain. The published […]

    https://rbfirehose.com/2026/04/17/toms-hardware-original-apollo-11-code-open-sourced-by-nasa-original-command-module-and-lunar-module-code-repos-are-now-public-domain-resources/
  5. Tom’s Hardware: Original Apollo 11 code open-sourced by NASA — original Command Module and Lunar Module code repos are now public domain resources. “The historic computer software code that took Apollo 11 to the moon has been open-sourced and is available for anyone to read, download, and tinker with. NASA’s Chris Garry made the code available on GitHub as public domain. The published […]

    https://rbfirehose.com/2026/04/17/toms-hardware-original-apollo-11-code-open-sourced-by-nasa-original-command-module-and-lunar-module-code-repos-are-now-public-domain-resources/
  6. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #Books #BookTokTech #HistoryOfComputing #TechNerd

  7. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #Books #BookTokTech #HistoryOfComputing #TechNerd

  8. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #Books #BookTokTech #HistoryOfComputing #TechNerd

  9. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #Books #BookTokTech #HistoryOfComputing #TechNerd

  10. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #Books #BookTokTech #HistoryOfComputing #TechNerd

  11. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #BookTokTech #HistoryOfComputing #TechNerd #books

  12. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #BookTokTech #HistoryOfComputing #TechNerd #books

  13. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #BookTokTech #HistoryOfComputing #TechNerd #books

  14. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #BookTokTech #HistoryOfComputing #TechNerd #books

  15. How did PCs take over the world? Fire in the Valley breaks down the early battles, bold ideas, and big personalities behind Apple, Microsoft, and the tech revolution.
    #BookTokTech #HistoryOfComputing #TechNerd #books

  16. A brief word of explanation - this is an old, old website, #historyofcomputing on the hoof, and a lot of stuff doesn't work. The last time I published to it was 2014, and even that was an attempt at revival after it had lain dormant since 2009. Some of it dates back to 1997 or so.

    Everything pertinent to Jumbo works. Everything else is ... well. Don't bother notifying me of things that don't work, let's put it that way.

    It's a miracle the blog works again, honestly.

  17. A brief word of explanation - this is an old, old website, #historyofcomputing on the hoof, and a lot of stuff doesn't work. The last time I published to it was 2014, and even that was an attempt at revival after it had lain dormant since 2009. Some of it dates back to 1997 or so.

    Everything pertinent to Jumbo works. Everything else is ... well. Don't bother notifying me of things that don't work, let's put it that way.

    It's a miracle the blog works again, honestly.

  18. A brief word of explanation - this is an old, old website, #historyofcomputing on the hoof, and a lot of stuff doesn't work. The last time I published to it was 2014, and even that was an attempt at revival after it had lain dormant since 2009. Some of it dates back to 1997 or so.

    Everything pertinent to Jumbo works. Everything else is ... well. Don't bother notifying me of things that don't work, let's put it that way.

    It's a miracle the blog works again, honestly.

  19. A brief word of explanation - this is an old, old website, #historyofcomputing on the hoof, and a lot of stuff doesn't work. The last time I published to it was 2014, and even that was an attempt at revival after it had lain dormant since 2009. Some of it dates back to 1997 or so.

    Everything pertinent to Jumbo works. Everything else is ... well. Don't bother notifying me of things that don't work, let's put it that way.

    It's a miracle the blog works again, honestly.

  20. I'm halfway through a reimplementation of Douglas Hofstadter's 1982 program Jumbo, the first implementation of his parallel terraced scan, and I've written a bit about it.

    Explanatory blog post at vivtek.com/blog/jum-sprint-don, and that links to a PDF paper, the code, and a few explanatory pages on the project. Feedback welcome! But I'll keep plugging away regardless. It's got its teeth into me now.

    #hofstadter #ai #historyofcomputing

  21. I'm halfway through a reimplementation of Douglas Hofstadter's 1982 program Jumbo, the first implementation of his parallel terraced scan, and I've written a bit about it.

    Explanatory blog post at vivtek.com/blog/jum-sprint-don, and that links to a PDF paper, the code, and a few explanatory pages on the project. Feedback welcome! But I'll keep plugging away regardless. It's got its teeth into me now.

    #hofstadter #ai #historyofcomputing

  22. I'm halfway through a reimplementation of Douglas Hofstadter's 1982 program Jumbo, the first implementation of his parallel terraced scan, and I've written a bit about it.

    Explanatory blog post at vivtek.com/blog/jum-sprint-don, and that links to a PDF paper, the code, and a few explanatory pages on the project. Feedback welcome! But I'll keep plugging away regardless. It's got its teeth into me now.

    #hofstadter #ai #historyofcomputing

  23. I'm halfway through a reimplementation of Douglas Hofstadter's 1982 program Jumbo, the first implementation of his parallel terraced scan, and I've written a bit about it.

    Explanatory blog post at vivtek.com/blog/jum-sprint-don, and that links to a PDF paper, the code, and a few explanatory pages on the project. Feedback welcome! But I'll keep plugging away regardless. It's got its teeth into me now.

    #hofstadter #ai #historyofcomputing

  24. New Interfaces article by CBI Senior Research Fellow William Aspray & Union College Prof. Emeritus David Hemmendinger "Using Reference Works to Study the Intellectual and Cultural History of Computing." It reflects on their terrific new book pictured below. #HistoryOfComputing #computers #AI #computerscience #technology #science #history

    Interfaces:
    cse.umn.edu/cbi/interfaces

  25. New Interfaces article by CBI Senior Research Fellow William Aspray & Union College Prof. Emeritus David Hemmendinger "Using Reference Works to Study the Intellectual and Cultural History of Computing." It reflects on their terrific new book pictured below. #HistoryOfComputing #computers #AI #computerscience #technology #science #history

    Interfaces:
    cse.umn.edu/cbi/interfaces

  26. New Interfaces article by CBI Senior Research Fellow William Aspray & Union College Prof. Emeritus David Hemmendinger "Using Reference Works to Study the Intellectual and Cultural History of Computing." It reflects on their terrific new book pictured below. #HistoryOfComputing #computers #AI #computerscience #technology #science #history

    Interfaces:
    cse.umn.edu/cbi/interfaces

  27. New Interfaces article by CBI Senior Research Fellow William Aspray & Union College Prof. Emeritus David Hemmendinger "Using Reference Works to Study the Intellectual and Cultural History of Computing." It reflects on their terrific new book pictured below. #HistoryOfComputing #computers #AI #computerscience #technology #science #history

    Interfaces:
    cse.umn.edu/cbi/interfaces

  28. New Interfaces article by CBI Senior Research Fellow William Aspray & Union College Prof. Emeritus David Hemmendinger "Using Reference Works to Study the Intellectual and Cultural History of Computing." It reflects on their terrific new book pictured below. #HistoryOfComputing #computers #AI #computerscience #technology #science #history

    Interfaces:
    cse.umn.edu/cbi/interfaces

  29. L'OKI IF-800 Model 50 de 1983 est fascinant :
    un ordinateur conçu comme infrastructure de bureau, avec Kanji natif et approche “système”.
    Il montre pourquoi le Japon, malgré sa maîtrise technique, a perdu la bataille des standards mondiaux.

    A lire : silicium.org/index.php/blog-ca

    #RetroComputing #HistoryOfComputing #JapaneseTech #OKI #IF800 #DigitalHistory

  30. L'OKI IF-800 Model 50 de 1983 est fascinant :
    un ordinateur conçu comme infrastructure de bureau, avec Kanji natif et approche “système”.
    Il montre pourquoi le Japon, malgré sa maîtrise technique, a perdu la bataille des standards mondiaux.

    A lire : silicium.org/index.php/blog-ca

    #RetroComputing #HistoryOfComputing #JapaneseTech #OKI #IF800 #DigitalHistory

  31. L'OKI IF-800 Model 50 de 1983 est fascinant :
    un ordinateur conçu comme infrastructure de bureau, avec Kanji natif et approche “système”.
    Il montre pourquoi le Japon, malgré sa maîtrise technique, a perdu la bataille des standards mondiaux.

    A lire : silicium.org/index.php/blog-ca

    #RetroComputing #HistoryOfComputing #JapaneseTech #OKI #IF800 #DigitalHistory

  32. L'OKI IF-800 Model 50 de 1983 est fascinant :
    un ordinateur conçu comme infrastructure de bureau, avec Kanji natif et approche “système”.
    Il montre pourquoi le Japon, malgré sa maîtrise technique, a perdu la bataille des standards mondiaux.

    A lire : silicium.org/index.php/blog-ca

    #RetroComputing #HistoryOfComputing #JapaneseTech #OKI #IF800 #DigitalHistory

  33. L'OKI IF-800 Model 50 de 1983 est fascinant :
    un ordinateur conçu comme infrastructure de bureau, avec Kanji natif et approche “système”.
    Il montre pourquoi le Japon, malgré sa maîtrise technique, a perdu la bataille des standards mondiaux.

    A lire : silicium.org/index.php/blog-ca

    #RetroComputing #HistoryOfComputing #JapaneseTech #OKI #IF800 #DigitalHistory

  34. En 1986, Compaq sort le Deskpro 386, premier PC 32 bits du marché.
    Moment clé : IBM perd le contrôle de l’évolution du PC.
    Un vrai tournant pour l’écosystème ouvert.

    #RetroComputing #HistoryOfComputing #PC #silicium #retrocomputing

  35. En 1986, Compaq sort le Deskpro 386, premier PC 32 bits du marché.
    Moment clé : IBM perd le contrôle de l’évolution du PC.
    Un vrai tournant pour l’écosystème ouvert.

    #RetroComputing #HistoryOfComputing #PC #silicium #retrocomputing

  36. En 1986, Compaq sort le Deskpro 386, premier PC 32 bits du marché.
    Moment clé : IBM perd le contrôle de l’évolution du PC.
    Un vrai tournant pour l’écosystème ouvert.

    #RetroComputing #HistoryOfComputing #PC #silicium #retrocomputing

  37. En 1986, Compaq sort le Deskpro 386, premier PC 32 bits du marché.
    Moment clé : IBM perd le contrôle de l’évolution du PC.
    Un vrai tournant pour l’écosystème ouvert.

    #RetroComputing #HistoryOfComputing #PC #silicium #retrocomputing

  38. En 1986, Compaq sort le Deskpro 386, premier PC 32 bits du marché.
    Moment clé : IBM perd le contrôle de l’évolution du PC.
    Un vrai tournant pour l’écosystème ouvert.

    #RetroComputing #HistoryOfComputing #PC #silicium #retrocomputing

  39. 📜 In the 1950s, Dr. Newell and Simon were developing the Logic Theory Machine to simulate human problem-solving. They faced a challenge: tracking an unpredictable number of logical statements. Early machines like ENIAC used fixed-size arrays, where the size had to be predefined.

    🤔Want to know how they solved this, given those limitations?

    👉 Read the full story here - "Story of The First Linked List" - priyabrata-paul-blog.hashnode.

    #HistoryOfComputing #DataStructures #LinkedList