#applehistory — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #applehistory, aggregated by home.social.
-
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
-
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
-
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
-
🔍 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? ⚰️💀
https://killedbyapple.theden.sh/ #digitalgraveyard #Applehistory #productfailures #techhumor #innovation #HackerNews #ngated -
🔍 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? ⚰️💀
https://killedbyapple.theden.sh/ #digitalgraveyard #Applehistory #productfailures #techhumor #innovation #HackerNews #ngated -
🔍 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? ⚰️💀
https://killedbyapple.theden.sh/ #digitalgraveyard #Applehistory #productfailures #techhumor #innovation #HackerNews #ngated -
🔍 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? ⚰️💀
https://killedbyapple.theden.sh/ #digitalgraveyard #Applehistory #productfailures #techhumor #innovation #HackerNews #ngated -
🔍 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? ⚰️💀
https://killedbyapple.theden.sh/ #digitalgraveyard #Applehistory #productfailures #techhumor #innovation #HackerNews #ngated -
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.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
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.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
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.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
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.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
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.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
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.
-
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.
-
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.
-
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.
-
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.
-
Happy Birthday, Apple //c.
4/24/1984 -- 42 years
#AppleIIc #AppleII #Apple2forever #Apple #applehistory #techhistory #tech #technology #retrocomputing #vintagecomputing #retrocomputers #CRT #photo #dither #Atkinsondithering #officespace #desk #vintage
-
Happy Birthday, Apple //c.
4/24/1984 -- 42 years
#AppleIIc #AppleII #Apple2forever #Apple #applehistory #techhistory #tech #technology #retrocomputing #vintagecomputing #retrocomputers #CRT #photo #dither #Atkinsondithering #officespace #desk #vintage
-
Happy Birthday, Apple //c.
4/24/1984 -- 42 years
#AppleIIc #AppleII #Apple2forever #Apple #applehistory #techhistory #tech #technology #retrocomputing #vintagecomputing #retrocomputers #CRT #photo #dither #Atkinsondithering #officespace #desk #vintage
-
Happy Birthday, Apple //c.
4/24/1984 -- 42 years
#AppleIIc #AppleII #Apple2forever #Apple #applehistory #techhistory #tech #technology #retrocomputing #vintagecomputing #retrocomputers #CRT #photo #dither #Atkinsondithering #officespace #desk #vintage
-
Happy Birthday, Apple //c.
4/24/1984 -- 42 years
#AppleIIc #AppleII #Apple2forever #Apple #applehistory #techhistory #tech #technology #retrocomputing #vintagecomputing #retrocomputers #CRT #photo #dither #Atkinsondithering #officespace #desk #vintage
-
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.
-
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.
-
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.
-
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.
-
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.
-
The heat sink that sunk the Apple III.
-
The heat sink that sunk the Apple III.
-
The heat sink that sunk the Apple III.
-
The heat sink that sunk the Apple III.
-
The heat sink that sunk the Apple III.
-
Bruce the Yak was Final Cut Pro’s Dogcow
https://web.brid.gy/r/https://512pixels.net/2026/04/bruce-the-yak-final-cut/
-
Bruce the Yak was Final Cut Pro’s Dogcow
https://web.brid.gy/r/https://512pixels.net/2026/04/bruce-the-yak-final-cut/
-
Bruce the Yak was Final Cut Pro’s Dogcow
https://web.brid.gy/r/https://512pixels.net/2026/04/bruce-the-yak-final-cut/
-
Bruce the Yak was Final Cut Pro’s Dogcow
https://web.brid.gy/r/https://512pixels.net/2026/04/bruce-the-yak-final-cut/
-
https://www.europesays.com/ie/420946/ When an engineer ‘angered’ Steve Jobs so much with his ‘Microsoft tablet’ stories that he told his team, we need to show … #Apple #Apple50thAnniversary #AppleHistory #BillGates #DavidPogue #Éire #IE #ipad #Ireland #Microsoft #MicrosoftOfficeForMac #MicrosoftRivalry #SteveJobs #Technology
-
For $200 more, you can get a MacBook Air
Joanna Stern talks Apple’s most imitated product.https://www.theverge.com/tech/901698/macbook-air-history
#apple #applenews #macbook #macbooknews #portablecomputer #macbookair #macbookairnews #tech #technews #appleproducts #macbookairhistory #applehistory #macbookhistory #apple50thanniversary
-
For $200 more, you can get a MacBook Air
Joanna Stern talks Apple’s most imitated product.https://www.theverge.com/tech/901698/macbook-air-history
#apple #applenews #macbook #macbooknews #portablecomputer #macbookair #macbookairnews #tech #technews #appleproducts #macbookairhistory #applehistory #macbookhistory #apple50thanniversary
-
For $200 more, you can get a MacBook Air
Joanna Stern talks Apple’s most imitated product.https://www.theverge.com/tech/901698/macbook-air-history
#apple #applenews #macbook #macbooknews #portablecomputer #macbookair #macbookairnews #tech #technews #appleproducts #macbookairhistory #applehistory #macbookhistory #apple50thanniversary
-
For $200 more, you can get a MacBook Air
Joanna Stern talks Apple’s most imitated product.https://www.theverge.com/tech/901698/macbook-air-history
#apple #applenews #macbook #macbooknews #portablecomputer #macbookair #macbookairnews #tech #technews #appleproducts #macbookairhistory #applehistory #macbookhistory #apple50thanniversary
-
For $200 more, you can get a MacBook Air
Joanna Stern talks Apple’s most imitated product.https://www.theverge.com/tech/901698/macbook-air-history
#apple #applenews #macbook #macbooknews #portablecomputer #macbookair #macbookairnews #tech #technews #appleproducts #macbookairhistory #applehistory #macbookhistory #apple50thanniversary
-
How Apple Could Have (Maybe) Saved the Mac Pro
https://web.brid.gy/r/https://512pixels.net/2026/03/how-apple-could-have-saved-the-mac-pro/
-
How Apple Could Have (Maybe) Saved the Mac Pro
https://web.brid.gy/r/https://512pixels.net/2026/03/how-apple-could-have-saved-the-mac-pro/
-
How Apple Could Have (Maybe) Saved the Mac Pro
https://web.brid.gy/r/https://512pixels.net/2026/03/how-apple-could-have-saved-the-mac-pro/
-
How Apple Could Have (Maybe) Saved the Mac Pro
https://web.brid.gy/r/https://512pixels.net/2026/03/how-apple-could-have-saved-the-mac-pro/
-
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.
-
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.
-
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.