News for hackers. Stuff that matters.
Re:Thoughts on a New Dylan Ecosystem by rayiner on Tuesday November 12, 2013 @09:12AM (#6717897)
I've always lamented that Ruby and the like caught on when Dylan didn't. At a time when most dynamic languages are still struggling without multi-threading or generational garbage collection (or hell, even correct lexical scoping!), Dylan has had a very sophisticated implementation for 15 years now. Open Dylan has native compilation, type inference, native threads, a sophisticated garbage collector, etc. The other side of the coin is, unfortunately, that it's hard to maintain such a sophisticated implementation without substantial manpower. The compiler is 100kloc of well-written but complex and dense code, and the runtime library is quite complex as well. That said, the Dylan Hackers are doing some really interesting work, e.g. building an LLVM backend for the compiler, so if you have an interest in the subject it's worth checking out.
Re:Thoughts on a New Dylan Ecosystem by tokenrove on Tuesday November 12, 2013 @11:54AM (#6718902)
I always figured it sat in a bad place, at least in terms of visibility, because Lisp hackers knew about it but mostly viewed it as an unnecessary compromise (why use Dylan when you can use CL?), whereas people outside Lisp either didn't know about it, or didn't understand what all the fuss was about. Which is too bad because it's a great language.
Re:Thoughts on a New Dylan Ecosystem by pjmlp on Tuesday November 12, 2013 @11:49AM (#6718860)
Yeah, if Apple hadn't ditched it, maybe it would even be Mac OS X main language instead of Objective-C.

Well, one can always dream.

Re:Thoughts on a New Dylan Ecosystem by mpweiher on Tuesday November 12, 2013 @04:56PM (#6721500)
Mac OS X's main language is Objective-C because it is essentially NeXTStep 5.0 and the basic libraries were mature Objective-C libraries. I don't see how Dylan would have entered the picture.
Re:Thoughts on a New Dylan Ecosystem by pjmlp on Tuesday November 12, 2013 @05:19PM (#6721683)
I know Objective-C since the NeXT days, even before Apple dreamed about buying NeXT.

As for Dylan, it was going to be Newton's application language, before the project was canned.

So playing "What If" scenarios, if the language stayed in Apple's control, and if NeXT was still bought, Dylan might have had a life in whatever form Mac OS X would have shaped itself.

Although this is a very unlikely scenario, Apple was actually not that sure that Objective-C would take off as it did.

This is why there was a Java/Cocoa bridge with first class treatment on the early days of Mac OS X, before focusing only on Objective-C.

Re:Thoughts on a New Dylan Ecosystem by vjoel on Tuesday November 12, 2013 @04:27PM (#6721272)
Also: generic functions. And hygienic macros. I miss those in ruby.