News for hackers. Stuff that matters.
Re:Open Dylan 2013.1 released by Someone on Thursday July 11, 2013 @05:55AM (#6025223)
Apple designed the language to ease the move of experimental (typically Lisp or Smalltalk) code into production (where it had to run faster, in less memory, etc). Tey wanted a Lisp that ran as fast and as memory efficient as C, so that they could write the OS in Lisp.

That's why they put a lot of thought into the sealing functionality (http://jim.studt.net/dirm/interim-36.html) and into limited types. For example, you can store a 'integer between zero and a hundred or letter of the alphabet or NULL' in a single byte. Expressing that in C is cumbersome, as you would need wrapper functions or macros, would need to remember using them, etc. A sufficiently advanced Dylan compiler could figure out a representation of its own.

Pascal-like syntax was bolted on later when they tried to bring the compiler to the masses. That, in turn, required serious thinking about the macro system.

And no, that didn't work out. There was a prerelease development environment, but they never managed to get this mainstream.

Re:Open Dylan 2013.1 released by pjmlp on Thursday July 11, 2013 @09:32AM (#6025880)
> And no, that didn't work out. There was a prerelease development environment, but they never managed to get this mainstream.

This was due to internal Apple politics, as Dylan was planed to be the system language for Newton, I don't remember any longer the full story but other group ended up getting the project.

Re:Open Dylan 2013.1 released by revaaron on Thursday July 11, 2013 @12:26PM (#6027059)
It's been a while since I've read the paper, but technical aspects like runtime size of binaries led to a bytecode compiled language like Smalltalk, leading to NewtonScript.