4 ms·

So Hy has different forms used than either Common Lisp, Scheme, or Clojure? That just makes me frustrated. I know Lisp is the urlang from which all dynamic lan

by pnathan 13y ago

So Hy has different forms used than either Common Lisp, Scheme, or Clojure? That just makes me frustrated. I know Lisp is the urlang from which all dynamic languages come from, I know that it's mutable into your personal tastes, but can we please standardize on a previously used set of forms? I respect and encourage people's desires to make a toylang, but if you want to promote it into "language for other people", things like portability become more important. I'm a common lisp guy, so obviously those are the best. ;-) But more importantly, I can run Common Lisp from before I was born. And I love that longjevity of my code and other people's code. http://docs.hylang.org/en/latest/ http://docs.hylang.org/en/latest/

lispm 13y ago
If he had just implemented a toy Scheme which adheres to R4RS or R%RS, then he could have leveraged the work of many people working on small Lisps.
- paultag 13y ago
  We don't have control of the runtime - the runtime is actually just Python -- in fact, a generated Hy .pyc can run on a system without Hy installed on it - so keeping it compliant to anything would just be insane. We're also taking from Python's work - working with MongoDB or using requests + clint to write a 2 minute API wrapper is like 5 lines of code in hy :)
paultag 13y ago
This started out as a joke for PyCon / teaching folks how to use Python AST, and it's grown to be kinda useful for a few things -- Macros aren't there yet, and the language is immature / special-snowflake about some things, but it's generally saneish. Since we do target Python AST we don't control the runtime (at all), since hy stored as a .pyc (or even use pdb to debug lisp in Python, wat) it's really (really) hard to build up a traditional lisp. C'mon over and hack with us!
- pnathan 13y ago
  Ah, thanks for the history. That provides context. I am afraid my contributions would be to provide rewrites and so forth to attempt to adhere to a subset of Common Lisp.
  - deleted 13y ago
    [deleted]

by pnathan 13y ago

lispm 13y ago

If he had just implemented a toy Scheme which adheres to R4RS or R%RS, then he could have leveraged the work of many people working on small Lisps.

paultag 13y ago
We don't have control of the runtime - the runtime is actually just Python -- in fact, a generated Hy .pyc can run on a system without Hy installed on it - so keeping it compliant to anything would just be insane. We're also taking from Python's work - working with MongoDB or using requests + clint to write a 2 minute API wrapper is like 5 lines of code in hy :)

paultag 13y ago

This started out as a joke for PyCon / teaching folks how to use Python AST, and it's grown to be kinda useful for a few things -- Macros aren't there yet, and the language is immature / special-snowflake about some things, but it's generally saneish. Since we do target Python AST we don't control the runtime (at all), since hy stored as a .pyc (or even use pdb to debug lisp in Python, wat) it's really (really) hard to build up a traditional lisp. C'mon over and hack with us!

pnathan 13y ago
Ah, thanks for the history. That provides context. I am afraid my contributions would be to provide rewrites and so forth to attempt to adhere to a subset of Common Lisp.
- deleted 13y ago
  [deleted]