home.social

#software-archaeology — Public Fediverse posts

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

fetched live
  1. Some protocols begin life not as RFCs, but as “read the source; that’s the spec.”

    I’m experimenting with AI agents to extract an implementable protocol specification from Python code. See diagram.

    Has anyone else used AI for protocol archaeology / reverse-specification?

    #ProtocolDesign #ReverseEngineering #SoftwareArchaeology #AIAgents #Python #Interoperability #DistributedSystems #OpenSource #MessagingProtocols #ProtocolSpecification #ImplementationDefined

  2. Some protocols begin life not as RFCs, but as “read the source; that’s the spec.”

    I’m experimenting with AI agents to extract an implementable protocol specification from Python code. See diagram.

    Has anyone else used AI for protocol archaeology / reverse-specification?

    #ProtocolDesign #ReverseEngineering #SoftwareArchaeology #AIAgents #Python #Interoperability #DistributedSystems #OpenSource #MessagingProtocols #ProtocolSpecification #ImplementationDefined

  3. Some protocols begin life not as RFCs, but as “read the source; that’s the spec.”

    I’m experimenting with AI agents to extract an implementable protocol specification from Python code. See diagram.

    Has anyone else used AI for protocol archaeology / reverse-specification?

    #ProtocolDesign #ReverseEngineering #SoftwareArchaeology #AIAgents #Python #Interoperability #DistributedSystems #OpenSource #MessagingProtocols #ProtocolSpecification #ImplementationDefined

  4. Some protocols begin life not as RFCs, but as “read the source; that’s the spec.”

    I’m experimenting with AI agents to extract an implementable protocol specification from Python code. See diagram.

    Has anyone else used AI for protocol archaeology / reverse-specification?

    #ProtocolDesign #ReverseEngineering #SoftwareArchaeology #AIAgents #Python #Interoperability #DistributedSystems #OpenSource #MessagingProtocols #ProtocolSpecification #ImplementationDefined

  5. Some protocols begin life not as RFCs, but as “read the source; that’s the spec.”

    I’m experimenting with AI agents to extract an implementable protocol specification from Python code. See diagram.

    Has anyone else used AI for protocol archaeology / reverse-specification?

    #ProtocolDesign #ReverseEngineering #SoftwareArchaeology #AIAgents #Python #Interoperability #DistributedSystems #OpenSource #MessagingProtocols #ProtocolSpecification #ImplementationDefined

  6. The first round of test generation for #DesmetC is complete, yielding over 30,000 test cases for integer comparison, integer arithmetic, and constant folding. Numerous bugs dating to the late 1980s were found and corrected. This is now out for review as pull request 9.

    #retrocomputing #softwarearchaeology

  7. The first round of test generation for #DesmetC is complete, yielding over 30,000 test cases for integer comparison, integer arithmetic, and constant folding. Numerous bugs dating to the late 1980s were found and corrected. This is now out for review as pull request 9.

    #retrocomputing #softwarearchaeology

  8. The first round of test generation for #DesmetC is complete, yielding over 30,000 test cases for integer comparison, integer arithmetic, and constant folding. Numerous bugs dating to the late 1980s were found and corrected. This is now out for review as pull request 9.

    #retrocomputing #softwarearchaeology

  9. The first round of test generation for #DesmetC is complete, yielding over 30,000 test cases for integer comparison, integer arithmetic, and constant folding. Numerous bugs dating to the late 1980s were found and corrected. This is now out for review as pull request 9.

    #retrocomputing #softwarearchaeology

  10. The first round of test generation for #DesmetC is complete, yielding over 30,000 test cases for integer comparison, integer arithmetic, and constant folding. Numerous bugs dating to the late 1980s were found and corrected. This is now out for review as pull request 9.

    #retrocomputing #softwarearchaeology

  11. Latest #DesmetC "explorations with machete and torch": the compiler source has numbered constants for each supported C datatype. Normally you'd use enum for this sort of thing, but this codebase used #defines. The constants were numbered in a strange order, and I wanted to re-sort them in the order of the "usual arithmetic conversions", to simplify some logic. This broke code-gen, emitting illegal instructions. Several hours later, I found that CCHAR=1 and CINT=2 were directly used in hex math determining which x86 opcode to emit. When I renumbered those constants, it caused absurd instructions to be generated. After correcting that problem, we are now back to self-hosting o.k.
    I'm hoping this will make it possible to retire a bunch of one-off type promotion logic scattered around the compiler, in favor of a few central functions closely mapping to the C89 standard.

    #retrocomputing #SoftwareArchaeology

  12. Latest #DesmetC "explorations with machete and torch": the compiler source has numbered constants for each supported C datatype. Normally you'd use enum for this sort of thing, but this codebase used #defines. The constants were numbered in a strange order, and I wanted to re-sort them in the order of the "usual arithmetic conversions", to simplify some logic. This broke code-gen, emitting illegal instructions. Several hours later, I found that CCHAR=1 and CINT=2 were directly used in hex math determining which x86 opcode to emit. When I renumbered those constants, it caused absurd instructions to be generated. After correcting that problem, we are now back to self-hosting o.k.
    I'm hoping this will make it possible to retire a bunch of one-off type promotion logic scattered around the compiler, in favor of a few central functions closely mapping to the C89 standard.

    #retrocomputing #SoftwareArchaeology

  13. Latest #DesmetC "explorations with machete and torch": the compiler source has numbered constants for each supported C datatype. Normally you'd use enum for this sort of thing, but this codebase used #defines. The constants were numbered in a strange order, and I wanted to re-sort them in the order of the "usual arithmetic conversions", to simplify some logic. This broke code-gen, emitting illegal instructions. Several hours later, I found that CCHAR=1 and CINT=2 were directly used in hex math determining which x86 opcode to emit. When I renumbered those constants, it caused absurd instructions to be generated. After correcting that problem, we are now back to self-hosting o.k.
    I'm hoping this will make it possible to retire a bunch of one-off type promotion logic scattered around the compiler, in favor of a few central functions closely mapping to the C89 standard.

    #retrocomputing #SoftwareArchaeology

  14. Latest #DesmetC "explorations with machete and torch": the compiler source has numbered constants for each supported C datatype. Normally you'd use enum for this sort of thing, but this codebase used #defines. The constants were numbered in a strange order, and I wanted to re-sort them in the order of the "usual arithmetic conversions", to simplify some logic. This broke code-gen, emitting illegal instructions. Several hours later, I found that CCHAR=1 and CINT=2 were directly used in hex math determining which x86 opcode to emit. When I renumbered those constants, it caused absurd instructions to be generated. After correcting that problem, we are now back to self-hosting o.k.
    I'm hoping this will make it possible to retire a bunch of one-off type promotion logic scattered around the compiler, in favor of a few central functions closely mapping to the C89 standard.

    #retrocomputing #SoftwareArchaeology

  15. Latest #DesmetC "explorations with machete and torch": the compiler source has numbered constants for each supported C datatype. Normally you'd use enum for this sort of thing, but this codebase used #defines. The constants were numbered in a strange order, and I wanted to re-sort them in the order of the "usual arithmetic conversions", to simplify some logic. This broke code-gen, emitting illegal instructions. Several hours later, I found that CCHAR=1 and CINT=2 were directly used in hex math determining which x86 opcode to emit. When I renumbered those constants, it caused absurd instructions to be generated. After correcting that problem, we are now back to self-hosting o.k.
    I'm hoping this will make it possible to retire a bunch of one-off type promotion logic scattered around the compiler, in favor of a few central functions closely mapping to the C89 standard.

    #retrocomputing #SoftwareArchaeology

  16. Ah, another brave soul attempts to shoehorn #xv6 into the almighty #SiFive HiFive Unmatched board. 🤡 Because #porting an archaic educational OS to a niche board is exactly what the world needed right now. 🙄 #GitHub, of course, stands by to witness this monumental achievement in software archaeology. 🥳
    github.com/eyengin/xv6-riscv-u #HiFiveUnmatched #softwarearchaeology #educationalOS #HackerNews #ngated

  17. Ah, another brave soul attempts to shoehorn #xv6 into the almighty #SiFive HiFive Unmatched board. 🤡 Because #porting an archaic educational OS to a niche board is exactly what the world needed right now. 🙄 #GitHub, of course, stands by to witness this monumental achievement in software archaeology. 🥳
    github.com/eyengin/xv6-riscv-u #HiFiveUnmatched #softwarearchaeology #educationalOS #HackerNews #ngated

  18. Ah, another brave soul attempts to shoehorn #xv6 into the almighty #SiFive HiFive Unmatched board. 🤡 Because #porting an archaic educational OS to a niche board is exactly what the world needed right now. 🙄 #GitHub, of course, stands by to witness this monumental achievement in software archaeology. 🥳
    github.com/eyengin/xv6-riscv-u #HiFiveUnmatched #softwarearchaeology #educationalOS #HackerNews #ngated

  19. Ah, another brave soul attempts to shoehorn #xv6 into the almighty #SiFive HiFive Unmatched board. 🤡 Because #porting an archaic educational OS to a niche board is exactly what the world needed right now. 🙄 #GitHub, of course, stands by to witness this monumental achievement in software archaeology. 🥳
    github.com/eyengin/xv6-riscv-u #HiFiveUnmatched #softwarearchaeology #educationalOS #HackerNews #ngated

  20. 🚀 From 68k ROM to bootable OS in 72 hours
    📄 Working paper: zenodo.org/records/17196870
    💻 GitHub: github.com/Kelsidavis/System7
    What legacy system would you want to see preserved or modernized with this approach?

  21. 🚀 From 68k ROM to bootable OS in 72 hours
    📄 Working paper: zenodo.org/records/17196870
    💻 GitHub: github.com/Kelsidavis/System7
    What legacy system would you want to see preserved or modernized with this approach?
    #ReverseEngineering #AI #LegacySystems #SoftwareArchaeology #TechInnovation #ComputerHistory #OpenScience

  22. 🚀 From 68k ROM to bootable OS in 72 hours
    📄 Working paper: zenodo.org/records/17196870
    💻 GitHub: github.com/Kelsidavis/System7
    What legacy system would you want to see preserved or modernized with this approach?
    #ReverseEngineering #AI #LegacySystems #SoftwareArchaeology #TechInnovation #ComputerHistory #OpenScience

  23. 🚀 From 68k ROM to bootable OS in 72 hours
    📄 Working paper: zenodo.org/records/17196870
    💻 GitHub: github.com/Kelsidavis/System7
    What legacy system would you want to see preserved or modernized with this approach?
    #ReverseEngineering #AI #LegacySystems #SoftwareArchaeology #TechInnovation #ComputerHistory #OpenScience

  24. 🚀 From 68k ROM to bootable OS in 72 hours
    📄 Working paper: zenodo.org/records/17196870
    💻 GitHub: github.com/Kelsidavis/System7
    What legacy system would you want to see preserved or modernized with this approach?
    #ReverseEngineering #AI #LegacySystems #SoftwareArchaeology #TechInnovation #ComputerHistory #OpenScience

  25. 🪨🛠️ New Post
    2025 is the 40th birthday of the Commodore Amiga. It is *also* the 40th birthday of Deluxe Paint. Our first retrospective examines this classic hardware/software combo.
    #RetroComputing #SoftwareArchaeology #Amiga #DeluxePaint #StoneTools

    stonetools.ghost.io/deluxepaint-amiga/

  26. 🪨🛠️ New Post
    2025 is the 40th birthday of the Commodore Amiga. It is *also* the 40th birthday of Deluxe Paint. Our first retrospective examines this classic hardware/software combo.
    #RetroComputing #SoftwareArchaeology #Amiga #DeluxePaint #StoneTools

    stonetools.ghost.io/deluxepaint-amiga/

  27. 🪨🛠️ New Post
    2025 is the 40th birthday of the Commodore Amiga. It is *also* the 40th birthday of Deluxe Paint. Our first retrospective examines this classic hardware/software combo.
    #RetroComputing #SoftwareArchaeology #Amiga #DeluxePaint #StoneTools

    stonetools.ghost.io/deluxepaint-amiga/

  28. 🪨🛠️ New Post
    2025 is the 40th birthday of the Commodore Amiga. It is *also* the 40th birthday of Deluxe Paint. Our first retrospective examines this classic hardware/software combo.
    #RetroComputing #SoftwareArchaeology #Amiga #DeluxePaint #StoneTools

    stonetools.ghost.io/deluxepaint-amiga/

  29. I've been working diligently on a #retrocomputing project which just soft-launched. You may shake your head, "Not another retro blog!" but I promise, this one's a little different; in-depth, hands-on examinations of the productivity software of the 8/16-bit era. It's called "Stone Tools"
    #computerhistory #officeofthefuture #softwarearchaeology #stonetools

    mastodon.social/@stonetoolsblo

  30. I've been working diligently on a #retrocomputing project which just soft-launched. You may shake your head, "Not another retro blog!" but I promise, this one's a little different; in-depth, hands-on examinations of the productivity software of the 8/16-bit era. It's called "Stone Tools"
    #computerhistory #officeofthefuture #softwarearchaeology #stonetools

    mastodon.social/@stonetoolsblo

  31. I've been working diligently on a project which just soft-launched. You may shake your head, "Not another retro blog!" but I promise, this one's a little different; in-depth, hands-on examinations of the productivity software of the 8/16-bit era. It's called "Stone Tools"

    mastodon.social/@stonetoolsblo

  32. I've been working diligently on a #retrocomputing project which just soft-launched. You may shake your head, "Not another retro blog!" but I promise, this one's a little different; in-depth, hands-on examinations of the productivity software of the 8/16-bit era. It's called "Stone Tools"
    #computerhistory #officeofthefuture #softwarearchaeology #stonetools

    mastodon.social/@stonetoolsblo

  33. I've been working diligently on a #retrocomputing project which just soft-launched. You may shake your head, "Not another retro blog!" but I promise, this one's a little different; in-depth, hands-on examinations of the productivity software of the 8/16-bit era. It's called "Stone Tools"
    #computerhistory #officeofthefuture #softwarearchaeology #stonetools

    mastodon.social/@stonetoolsblo

  34. We’re live! 🪨🛠️ Stone Tools has soft-launched, with the first proper post coming later this week. If you think retro-computing means more than just games, you’re in the right place. Hands-on, in-depth examinations of the productivity software from the retro "golden age" (1977-1995)
    #RetroComputing #ComputerHistory #OfficeOfTheFuture #SoftwareArchaeology #StoneTools

    stonetools.ghost.io/introducin

  35. We’re live! 🪨🛠️ Stone Tools has soft-launched, with the first proper post coming later this week. If you think retro-computing means more than just games, you’re in the right place. Hands-on, in-depth examinations of the productivity software from the retro "golden age" (1977-1995)
    #RetroComputing #ComputerHistory #OfficeOfTheFuture #SoftwareArchaeology #StoneTools

    stonetools.ghost.io/introducin

  36. We’re live! 🪨🛠️ Stone Tools has soft-launched, with the first proper post coming later this week. If you think retro-computing means more than just games, you’re in the right place. Hands-on, in-depth examinations of the productivity software from the retro "golden age" (1977-1995)
    #RetroComputing #ComputerHistory #OfficeOfTheFuture #SoftwareArchaeology #StoneTools

    stonetools.ghost.io/introducin

  37. We’re live! 🪨🛠️ Stone Tools has soft-launched, with the first proper post coming later this week. If you think retro-computing means more than just games, you’re in the right place. Hands-on, in-depth examinations of the productivity software from the retro "golden age" (1977-1995)
    #RetroComputing #ComputerHistory #OfficeOfTheFuture #SoftwareArchaeology #StoneTools

    stonetools.ghost.io/introducin

  38. We’re live! 🪨🛠️ Stone Tools has soft-launched, with the first proper post coming later this week. If you think retro-computing means more than just games, you’re in the right place. Hands-on, in-depth examinations of the productivity software from the retro "golden age" (1977-1995)
    #RetroComputing #ComputerHistory #OfficeOfTheFuture #SoftwareArchaeology #StoneTools

    stonetools.ghost.io/introducin

  39. #Gravit Designer vs. #Corel Vector (4#4)

    Mit diesem gvdesign Parser (#gvPa) wollen wir ermitteln, wieviel Elemente, Ebenen, Bitmaps, Fonts etc. enthalten sind.

    So könnten wir einschätzen was mit SVG geht. Welche anderern Fileformate Schriften, Layer & Effekte am besten unterstützt.

    Zum Schluß wollen wir untersuchen, welche Lösungen für die Zukunft geeignet wäre um flüssig mit Bitmaps und Vektor zusammen zu arbeiten.

    Lust? Meld dich!

    \__
    #ReverseEngineer #Marktforschung #SoftwareArchaeology

  40. #Gravit Designer vs. #Corel Vector (4#4)

    Mit diesem gvdesign Parser (#gvPa) wollen wir ermitteln, wieviel Elemente, Ebenen, Bitmaps, Fonts etc. enthalten sind.

    So könnten wir einschätzen was mit SVG geht. Welche anderern Fileformate Schriften, Layer & Effekte am besten unterstützt.

    Zum Schluß wollen wir untersuchen, welche Lösungen für die Zukunft geeignet wäre um flüssig mit Bitmaps und Vektor zusammen zu arbeiten.

    Lust? Meld dich!

    \__
    #ReverseEngineer #Marktforschung #SoftwareArchaeology

  41. #Gravit Designer vs. #Corel Vector (4#4)

    Mit diesem gvdesign Parser (#gvPa) wollen wir ermitteln, wieviel Elemente, Ebenen, Bitmaps, Fonts etc. enthalten sind.

    So könnten wir einschätzen was mit SVG geht. Welche anderern Fileformate Schriften, Layer & Effekte am besten unterstützt.

    Zum Schluß wollen wir untersuchen, welche Lösungen für die Zukunft geeignet wäre um flüssig mit Bitmaps und Vektor zusammen zu arbeiten.

    Lust? Meld dich!

    \__
    #ReverseEngineer #Marktforschung #SoftwareArchaeology

  42. #Gravit Designer vs. #Corel Vector (4#4)

    Mit diesem gvdesign Parser (#gvPa) wollen wir ermitteln, wieviel Elemente, Ebenen, Bitmaps, Fonts etc. enthalten sind.

    So könnten wir einschätzen was mit SVG geht. Welche anderern Fileformate Schriften, Layer & Effekte am besten unterstützt.

    Zum Schluß wollen wir untersuchen, welche Lösungen für die Zukunft geeignet wäre um flüssig mit Bitmaps und Vektor zusammen zu arbeiten.

    Lust? Meld dich!

    \__
    #ReverseEngineer #Marktforschung #SoftwareArchaeology

  43. Ich hatte vergessen WIE lahm #Subversion war.

    Hätte aber auch prima ohne Erinnerung daran weiterleben können.

    #Computerarchäologie #softwarearchaeology #SVN
  44. Ich hatte vergessen WIE lahm #Subversion war.

    Hätte aber auch prima ohne Erinnerung daran weiterleben können.

    #Computerarchäologie #softwarearchaeology #SVN
  45. Ich hatte vergessen WIE lahm #Subversion war.

    Hätte aber auch prima ohne Erinnerung daran weiterleben können.

    #Computerarchäologie #softwarearchaeology #SVN