4 ms·
When reading about Dylan, it seems one of it's main selling points is "everything is an object." But nowadays, that's true in many other dynamic languages like
by bjourne 13y ago
When reading about Dylan, it seems one of it's main selling points is "everything is an object." But nowadays, that's true in many other dynamic languages like Python, Ruby and Clojure. Macros are everywhere and you can even add them to Python if you want to using third party modules. Though I've never felt the need because Python's syntax is excellent as it is.
For me it is very hard to see what Dylan brings to the table. It's nieche is already filled by more popular languages.
- sspiff 13y agoI understand where your coming from. For me, the selling point of Dylan is that it gives me many of the things I like from dynamic languages, like Ruby, but also gives me static typing (and type inference), relatively high performance and a compiler that catches a lot of problems before I run my code. Different people like different things, and while I love Ruby, static typing does catch a lot of problems earlier on.
- kaoD 13y agoBut what does it bring to the table compared to other typed languages with dynamic features (or the other way around, e.g. TypedClojure, TypeScript...) and bigger ecosystems?
- sspiff 13y agoI'm not familiar with TypedClojure or TypeScript, so I feel unqualified to answer your question. I'll attempt to answer anyway, because this is the Internet. At first glance they seem like subsets/dialects of other languages, which would reduce the benefits they get from their "parent" ecosystem? Similar to JRuby and Java, where I always felt a reluctance to interact with the Java side. That said, Dylan has a pretty neat FFI, and it's simple to wrap C libraries into Dylan-looking interfaces, so at least for me it benefits a lot from the plethora of C libraries out there. (I realize FFI is available to almost all languages, and doesn't really mean libraries are available to Dylan, but I find it very comfortable to bridge C and Dylan through its FFI.)
- planckscnst 13y agoHave you seen rust-activesupport? [1] It provides ActiveSupport-ey things like 2.days().from_now() in Rust, which has a very nice type system. [1] https://github.com/wycats/rust-activesupport https://github.com/wycats/rust-activesupport
- BruceM 13y agoA Common Lisp-style condition system is a pretty key thing for me. It is highly readable. And you can use '!' and '?' in names! An optimized implementation of multimethods is always nice. The ability to apply optional static typing is great for putting stuff into production and feeling good about it. Having multiple return values, keyword arguments and rest arguments is nice (and yes, Python can do much of that).
- coldtea 13y ago>It is highly readable. And you can use '!' and '?' in names! Somehow this feels a little contradictory.
- grdvnl 13y agoWhy do you feel it is contradictory? I think having method names end with "?" whenever they return a boolean value is quite intuitive. They seem to stand out more than having such method names start with "is" or "has". YMMV.
- experimentsin 13y agoLooking back at some Dylan code again now, I still find its richer, Lisp-derived, hyphenated naming approach more readable-and-expressive than either camelCase or underscore_separated identifiers. When Dylan switched from Lisp syntax this was something that was fretted over an awful lot, for obvious reasons, but we went with it and it worked fine. I'd love to see some other algebraic (non Lisp) syntax language get more creative in this direction again one day.
- aerique 13y agoIt isn't. Common Lisp and Scheme can do this as well and I like the look of predicate functions like "list?" or "number?": (list? object) (number? 1) => returns true (number? "abc") => returns false It isn't really necessary for a language to support this, but it is a nice detail if one preferred such a style. I think the custom is to use "!" in functions with side-effects.
- lispm 13y agoApple designed it as a replacement for languages like C++, now Objective-C, Java, C#. Stuff like Apple Keynote, Apple Pages, Apple's Xcode, Apple Mail, Contacts, Calendar, and the Apps on mobile devices like the iPhone and iPad would have been written in Dylan. Applications which Apple now writes in Objective-C. Apple already had an Operating System for an ARM-based computer written in an early version of Dylan (with some help of a C++ based kernel). It also tried to develop some Mac-based prototype applications: an interface builder and I think there was a 'Finder' written in Dylan.
- AndreasFrom 13y agoClojure, like Java, has primitives. And I don't understand why you'd include it anyway, as functions are the primary form of abstraction in Clojure.
- pjmlp 13y ago> For me it is very hard to see what Dylan brings to the table. It's nieche is already filled by more popular languages. A dynamic language with native code compiler and language features suitable for both application and systems programming. Plus being a Lisp like language with a more friendly syntax for those scared of parenthesis.