home.social

#applehistory — Public Fediverse posts

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

fetched live
  1. Remember Antennagate? A 47-minute video of Apple answering questions about the iPhone 4’s signal trouble has resurfaced. It’s a revealing look at a defining tech controversy.

    cryovex.com/antennagate-video-

    #Antennagate #iPhone4 #AppleHistory

  2. Remember Antennagate? A 47-minute video of Apple answering questions about the iPhone 4’s signal trouble has resurfaced. It’s a revealing look at a defining tech controversy.

    cryovex.com/antennagate-video-

    #Antennagate #iPhone4 #AppleHistory

  3. Remember Antennagate? A 47-minute video of Apple answering questions about the iPhone 4’s signal trouble has resurfaced. It’s a revealing look at a defining tech controversy.

    cryovex.com/antennagate-video-

    #Antennagate #iPhone4 #AppleHistory

  4. Remember Antennagate? A 47-minute video of Apple answering questions about the iPhone 4’s signal trouble has resurfaced. It’s a revealing look at a defining tech controversy.

    cryovex.com/antennagate-video-

    #Antennagate #iPhone4 #AppleHistory

  5. Geoffrey Cain points out that Steve Jobs’ reality‑distortion field propelled NeXT forward, but it also blinded him to his own biggest breakthrough – object‑oriented programming, the core of today’s Apple software. Is our hype ever our blind spot? youtube.com/shorts/vnqxatJagbg #SteveJobs #NeXT #AppleHistory

  6. Geoffrey Cain points out that Steve Jobs’ reality‑distortion field propelled NeXT forward, but it also blinded him to his own biggest breakthrough – object‑oriented programming, the core of today’s Apple software. Is our hype ever our blind spot? youtube.com/shorts/vnqxatJagbg #SteveJobs #NeXT #AppleHistory

  7. Geoffrey Cain points out that Steve Jobs’ reality‑distortion field propelled NeXT forward, but it also blinded him to his own biggest breakthrough – object‑oriented programming, the core of today’s Apple software. Is our hype ever our blind spot? youtube.com/shorts/vnqxatJagbg

  8. Geoffrey Cain points out that Steve Jobs’ reality‑distortion field propelled NeXT forward, but it also blinded him to his own biggest breakthrough – object‑oriented programming, the core of today’s Apple software. Is our hype ever our blind spot? youtube.com/shorts/vnqxatJagbg #SteveJobs #NeXT #AppleHistory

  9. Ever wonder why every swipe, every drag-and-drop feels instinctive? 40 years ago Steve Jobs sparked a quiet software revolution: he championed object-oriented programming, the foundation of today’s iPhone UI. Geoffrey Cain, author of Steve Jobs in Exile, unpacks it in this short. 🎧 youtube.com/shorts/vnqxatJagbg #SteveJobs #ObjectOrientedProgramming #NeXT #AppleHistory

  10. Ever wonder why every swipe, every drag-and-drop feels instinctive? 40 years ago Steve Jobs sparked a quiet software revolution: he championed object-oriented programming, the foundation of today’s iPhone UI. Geoffrey Cain, author of Steve Jobs in Exile, unpacks it in this short. 🎧 youtube.com/shorts/vnqxatJagbg

  11. Apple pushed him out. He built NeXT. He turned Pixar into a cinema giant. Then Apple brought him back. What followed was one of the greatest comebacks in business history
    #SteveJobs #AppleHistory #Pixar #books #bookreviews
    grandpasbookreviews.blogspot.c

  12. Apple pushed him out. He built NeXT. He turned Pixar into a cinema giant. Then Apple brought him back. What followed was one of the greatest comebacks in business history
    #SteveJobs #AppleHistory #Pixar #books #bookreviews
    grandpasbookreviews.blogspot.c

  13. Apple pushed him out. He built NeXT. He turned Pixar into a cinema giant. Then Apple brought him back. What followed was one of the greatest comebacks in business history
    #SteveJobs #AppleHistory #Pixar #books #bookreviews
    grandpasbookreviews.blogspot.c

  14. Apple pushed him out. He built NeXT. He turned Pixar into a cinema giant. Then Apple brought him back. What followed was one of the greatest comebacks in business history
    #SteveJobs #AppleHistory #Pixar #books #bookreviews
    grandpasbookreviews.blogspot.c

  15. Steve Jobs asked Walter Isaacson to write his biography. He wanted the truth told. Nothing was off limits. The result is one of the best biographies ever written. 5 stars.
    #SteveJobs #WalterIsaacson #AppleHistory #books #bookreviews
    grandpasbookreviews.blogspot.c

  16. Steve Jobs asked Walter Isaacson to write his biography. He wanted the truth told. Nothing was off limits. The result is one of the best biographies ever written. 5 stars.
    #SteveJobs #WalterIsaacson #AppleHistory #books #bookreviews
    grandpasbookreviews.blogspot.c

  17. Steve Jobs asked Walter Isaacson to write his biography. He wanted the truth told. Nothing was off limits. The result is one of the best biographies ever written. 5 stars.
    #SteveJobs #WalterIsaacson #AppleHistory #books #bookreviews
    grandpasbookreviews.blogspot.c

  18. Steve Jobs asked Walter Isaacson to write his biography. He wanted the truth told. Nothing was off limits. The result is one of the best biographies ever written. 5 stars.
    #SteveJobs #WalterIsaacson #AppleHistory #books #bookreviews
    grandpasbookreviews.blogspot.c

  19. 1984. A little beige box changed everything. 💻🍏

    Not the fastest. Not the cheapest. But it had a mouse. Icons. Windows. A computer your grandmother could use.

    Jobs stole fire from Xerox PARC. Then he lit his own. Kicked off the Lisa project, he took Macintosh and made it more Lisa than Lisa.

    "Insanely great." That's what he said.

    The rest is history.

    #Macintosh #SteveJobs #AppleHistory #GUI #InsanelyGreat

  20. 1984. A little beige box changed everything. 💻🍏

    Not the fastest. Not the cheapest. But it had a mouse. Icons. Windows. A computer your grandmother could use.

    Jobs stole fire from Xerox PARC. Then he lit his own. Kicked off the Lisa project, he took Macintosh and made it more Lisa than Lisa.

    "Insanely great." That's what he said.

    The rest is history.

    #Macintosh #SteveJobs #AppleHistory #GUI #InsanelyGreat

  21. 1984. A little beige box changed everything. 💻🍏

    Not the fastest. Not the cheapest. But it had a mouse. Icons. Windows. A computer your grandmother could use.

    Jobs stole fire from Xerox PARC. Then he lit his own. Kicked off the Lisa project, he took Macintosh and made it more Lisa than Lisa.

    "Insanely great." That's what he said.

    The rest is history.

    #Macintosh #SteveJobs #AppleHistory #GUI #InsanelyGreat

  22. I stood in front of this little machine and was completely mesmerized.

    Apple Macintosh Classic II (1991) - the very last black-and-white compact Macintosh Apple ever made.

    9-inch monochrome screen, 16 MHz 68030 processor, perfect all-in-one design. Even after 35 years it still looks incredibly clean, elegant and timeless.

    Sometimes the old machines have a "soul" that modern computers just can't replicate anymore.
    Or it's just me getting old now 🥲

    #Macintosh #VintageApple #RetroComputing #AppleHistory #History #Computer #Apple #Mac #Museum #Blog #Thoughts

  23. I stood in front of this little machine and was completely mesmerized.

    Apple Macintosh Classic II (1991) - the very last black-and-white compact Macintosh Apple ever made.

    9-inch monochrome screen, 16 MHz 68030 processor, perfect all-in-one design. Even after 35 years it still looks incredibly clean, elegant and timeless.

    Sometimes the old machines have a "soul" that modern computers just can't replicate anymore.
    Or it's just me getting old now 🥲

    #Macintosh #VintageApple #RetroComputing #AppleHistory #History #Computer #Apple #Mac #Museum #Blog #Thoughts

  24. I stood in front of this little machine and was completely mesmerized.

    Apple Macintosh Classic II (1991) - the very last black-and-white compact Macintosh Apple ever made.

    9-inch monochrome screen, 16 MHz 68030 processor, perfect all-in-one design. Even after 35 years it still looks incredibly clean, elegant and timeless.

    Sometimes the old machines have a "soul" that modern computers just can't replicate anymore.
    Or it's just me getting old now 🥲

    #Macintosh #VintageApple #RetroComputing #AppleHistory #History #Computer #Apple #Mac #Museum #Blog #Thoughts

  25. 🔍 Behold the digital graveyard for Apple's dearly departed products, curated by someone with too much time on their hands. 😂 Apparently, listing Apple's product fatalities is a full-time hobby now—because why innovate when you can just alphabetize corporate tombstones? ⚰️💀
    killedbyapple.theden.sh/ #digitalgraveyard #Applehistory #productfailures #techhumor #innovation #HackerNews #ngated

  26. 🔍 Behold the digital graveyard for Apple's dearly departed products, curated by someone with too much time on their hands. 😂 Apparently, listing Apple's product fatalities is a full-time hobby now—because why innovate when you can just alphabetize corporate tombstones? ⚰️💀
    killedbyapple.theden.sh/ #digitalgraveyard #Applehistory #productfailures #techhumor #innovation #HackerNews #ngated

  27. 🔍 Behold the digital graveyard for Apple's dearly departed products, curated by someone with too much time on their hands. 😂 Apparently, listing Apple's product fatalities is a full-time hobby now—because why innovate when you can just alphabetize corporate tombstones? ⚰️💀
    killedbyapple.theden.sh/ #digitalgraveyard #Applehistory #productfailures #techhumor #innovation #HackerNews #ngated

  28. 🔍 Behold the digital graveyard for Apple's dearly departed products, curated by someone with too much time on their hands. 😂 Apparently, listing Apple's product fatalities is a full-time hobby now—because why innovate when you can just alphabetize corporate tombstones? ⚰️💀
    killedbyapple.theden.sh/ #digitalgraveyard #Applehistory #productfailures #techhumor #innovation #HackerNews #ngated

  29. In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).

    My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.

    But I still think there could be things the Scheme community would want to glean from this snapshot of history.

    I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.

    [0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
    nhplace.com/kent/History/dylan

    [1] Ralph Conditions (part 1 of 2)
    nhplace.com/kent/History/dylan

    [2] Ralph Conditions (part 2 of 2)
    nhplace.com/kent/History/dylan

    cc @sigue @ramin_hal9001 @screwlisp

    #DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject

  30. In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).

    My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.

    But I still think there could be things the Scheme community would want to glean from this snapshot of history.

    I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.

    [0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
    nhplace.com/kent/History/dylan

    [1] Ralph Conditions (part 1 of 2)
    nhplace.com/kent/History/dylan

    [2] Ralph Conditions (part 2 of 2)
    nhplace.com/kent/History/dylan

    cc @sigue @ramin_hal9001 @screwlisp

    #DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject

  31. In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).

    My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.

    But I still think there could be things the Scheme community would want to glean from this snapshot of history.

    I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.

    [0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
    nhplace.com/kent/History/dylan

    [1] Ralph Conditions (part 1 of 2)
    nhplace.com/kent/History/dylan

    [2] Ralph Conditions (part 2 of 2)
    nhplace.com/kent/History/dylan

    cc @sigue @ramin_hal9001 @screwlisp

    #DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject

  32. In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).

    My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.

    But I still think there could be things the Scheme community would want to glean from this snapshot of history.

    I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.

    [0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
    nhplace.com/kent/History/dylan

    [1] Ralph Conditions (part 1 of 2)
    nhplace.com/kent/History/dylan

    [2] Ralph Conditions (part 2 of 2)
    nhplace.com/kent/History/dylan

    cc @sigue @ramin_hal9001 @screwlisp

    #DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject

  33. 42 years ago today (1984), Apple released the Apple IIc.

    It was their first “portable” computer — sort of. No built-in display or battery, but compact, lightweight, and ready to go with a handle. Basically the MacBook Air of its floppy-disk era.

    #AppleIIc #RetroComputing #AppleHistory #VintageTech #apple

  34. 42 years ago today (1984), Apple released the Apple IIc.

    It was their first “portable” computer — sort of. No built-in display or battery, but compact, lightweight, and ready to go with a handle. Basically the MacBook Air of its floppy-disk era.

    #AppleIIc #RetroComputing #AppleHistory #VintageTech #apple

  35. 42 years ago today (1984), Apple released the Apple IIc.

    It was their first “portable” computer — sort of. No built-in display or battery, but compact, lightweight, and ready to go with a handle. Basically the MacBook Air of its floppy-disk era.

    #AppleIIc #RetroComputing #AppleHistory #VintageTech #apple

  36. 42 years ago today (1984), Apple released the Apple IIc.

    It was their first “portable” computer — sort of. No built-in display or battery, but compact, lightweight, and ready to go with a handle. Basically the MacBook Air of its floppy-disk era.

    #AppleIIc #RetroComputing #AppleHistory #VintageTech #apple

  37. Wow! I’ve never heard of "General Magic" before. A fascinating short documentary about a company whose people, products and ideas were simply too far ahead of their time.

    #Apple #AppleHistory

    youtube.com/watch?v=zYQfTwQANbw

  38. Wow! I’ve never heard of "General Magic" before. A fascinating short documentary about a company whose people, products and ideas were simply too far ahead of their time.

    #Apple #AppleHistory

    youtube.com/watch?v=zYQfTwQANbw

  39. Wow! I’ve never heard of "General Magic" before. A fascinating short documentary about a company whose people, products and ideas were simply too far ahead of their time.

    #Apple #AppleHistory

    youtube.com/watch?v=zYQfTwQANbw

  40. Wow! I’ve never heard of "General Magic" before. A fascinating short documentary about a company whose people, products and ideas were simply too far ahead of their time.

    #Apple #AppleHistory

    youtube.com/watch?v=zYQfTwQANbw

  41. David Pogue ha pubblicato il libro Apple: The First 50 Years, che esplora la storia dell'azienda. La pubblicazione coincide con il 50° anniversario di Apple, fondata il 1° aprile 1976.

    #davidpogue #applehistory #techbook