Apple Dylan IDE (2014)

#1

Post by atjamielittle » Sat, Jun 03, 2017, 10:57 PM UTC

Apple Dylan IDE (2014)
web.archive.org

Re: Apple Dylan IDE (2014)

#2

Post by etchalon » Sun, Jun 04, 2017, 2:50 AM UTC

Some days, I still miss OS 8.

Re: Apple Dylan IDE (2014)

#3

Post by threeseed » Sun, Jun 04, 2017, 2:51 AM UTC

It's always interesting to look back on those days at Apple when they were so innovative and took so many risks when it came to software. Technologies like OpenDoc, Cyberdog, Hypercard, AppleScript, Taligent were really quite unique.

Re: Apple Dylan IDE (2014)

#4

Post by DaiPlusPlus » Sun, Jun 04, 2017, 3:02 AM UTC

What I like the most is the abstraction-away from plaintext source files. Imagine a C and C++ IDE that hid the (often ugly) source files from you put only exposed individual function definitions - it could automatically keep header files in-sync, for example, and automatically place each free-function or class member in the right file without manual refactoring.

(I still think it's outrageous that C is still a single-pass language - we shouldn't need separate simultaneous declaration and definitions any more)

Re: Apple Dylan IDE (2014)

#5

Post by atjamielittle » Sun, Jun 04, 2017, 3:03 AM UTC

threeseed wrote: post #3

It's always interesting to look back on those days at Apple when they were so innovative and took so many risks when it came to software. Technologies like OpenDoc, Cyberdog, Hypercard, AppleScript, Taligent were really quite unique.

I've really been enjoying reading Brent Simmons blog about his efforts to get Frontier running on modern macOS:

http://inessential.com/frontierdiary

I suppose that Apple Dylan was similar to Frontier in the sense that they were programming environments built around an object databases. Frontier was a shipping product though!

Re: Apple Dylan IDE (2014)

#6

Post by atjamielittle » Sun, Jun 04, 2017, 3:05 AM UTC

DaiPlusPlus wrote: post #4

What I like the most is the abstraction-away from plaintext source files. Imagine a C and C++ IDE that hid the (often ugly) source files from you put only exposed individual function definitions - it could automatically keep header files in-sync, for example, and automatically place each free-function or class member in the right file without manual refactoring. (I still think it's outrageous that C is still a single…

I think I would love this.

Re: Apple Dylan IDE (2014)

#7

Post by Volt » Sun, Jun 04, 2017, 3:14 AM UTC

threeseed wrote: post #3

It's always interesting to look back on those days at Apple when they were so innovative and took so many risks when it came to software. Technologies like OpenDoc, Cyberdog, Hypercard, AppleScript, Taligent were really quite unique.

Back when they actually had an R&D department.

Re: Apple Dylan IDE (2014)

#8

Post by whyenot » Sun, Jun 04, 2017, 3:16 AM UTC

Macintosh Common Lisp is another one. It was so much fun to use and worked so well with MacOS. Echoing etchalon's comment, sometimes I miss OS 8 (also 9).

https://en.wikipedia.org/wiki/Macintosh_Common_Lisp

Re: Apple Dylan IDE (2014)

#9

Post by tcbawo » Sun, Jun 04, 2017, 3:33 AM UTC

DaiPlusPlus wrote: post #4

What I like the most is the abstraction-away from plaintext source files. Imagine a C and C++ IDE that hid the (often ugly) source files from you put only exposed individual function definitions - it could automatically keep header files in-sync, for example, and automatically place each free-function or class member in the right file without manual refactoring. (I still think it's outrageous that C is still a single…

Unfortunately, preprocessing would make this difficult or impossible. Even with modern C++, people still rely on it.

Re: Apple Dylan IDE (2014)

#10

Post by mikek » Sun, Jun 04, 2017, 3:49 AM UTC

whyenot wrote: post #8

Macintosh Common Lisp is another one. It was so much fun to use and worked so well with MacOS. Echoing etchalon's comment, sometimes I miss OS 8 (also 9). https://en.wikipedia.org/wiki/Macintosh_Common_Lisp

Command-E for Execute!