News for hackers. Stuff that matters.
Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by xyzzyz on Tuesday November 29, 2011 @12:04PM (#3291086)
I'm sorry, but I cannot get excited over Yet Another Implementation of McCarthy's LISP[1]. If your Lisp had _any_ interesting feature, e.g. call/cc, or object system, or nifty macro system, or something else, then, maybe, but doing the the same old, trivial thing, again and again, does not seem very interesting for me.

We don't usually see yet another Brainfuck interpreter, or yet another Fibonacci queue implementation on HN's front page, so why LISP?

[1] - http://lib.store.yahoo.net/lib/paulgraham/jmc.lisp

Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by raganwald on Tuesday November 29, 2011 @12:31PM (#3291204)
(cranky

You know, we have the upvote arrow for things that excite you, and the “Go read something else and comment on it” feature for things that don’t float your boat.

Clearly this is not spam and it is not off-topic. So:

You asked the OP and/or your fellow HNers why they upvoted this onto the front page. I ask you, why this comment, what value does it add to my life to read about how smart and educated you are?

What about all the people who haven’t seen an implementation of McCarthy’s Lisp? Do they not deserve to find this interesting? Should they turn in their HN accounts and head over to reddit?

I wrote an implementation of Scheme in Java with macros, tail call optimization, lambda hoisting, a bunch of stuff. Yet I find this interesting. Is there something wrong with me?

)

Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by raganwald on Tuesday November 29, 2011 @12:41PM (#3291260)
Raganwald, you pretentious douche:

> I wrote an implementation of Scheme in Java with macros, tail call optimization, lambda hoisting, a bunch of stuff.

Greenspun’s Tenth Law is widely accepted, demonstrations of it in action add nothing of value to the programming community. Furthermore, writing a Scheme in Java is likely to be a project where you learned nothing of interest about Lisp or about Java.

—signed, Nikolai Bourbaki

Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by appamatto on Tuesday November 29, 2011 @12:53PM (#3291315)
Misapplication? I thought the Law was meant to describe accidental implementations of Lisp rather than overt ones.

In other words, "the complicated system you made _just happens_ to contain a Lisp, and if you had noticed that requirement in the first place its design would have been cleaner."

Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by raganwald on Tuesday November 29, 2011 @12:59PM (#3291341)
I think you have captured the spirit of the law. The project in question was the development of a scripting language for something-or-other, so this wasn’t an accidental implementation of Lisp, it was done with malice aforethought.
Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by apotheon on Tuesday November 29, 2011 @01:12PM (#3291399)
That's kind of an inappropriate response. Pointing out one has implemented Scheme with all the bells and whistles as a condition in which the implementor is still interested in Lisp implementations and similar stuff is not a pretension or a statement that it was some kind of tremendous feat.

I have a motorcycle, but I'm still interested in not only other motorcycles, but also bicycles. I don't think this makes me a pretentious douche.

Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by appamatto on Tuesday November 29, 2011 @01:46PM (#3291578)
Maybe he meant that his Java implementation of Scheme contains an ad-hoc implementation of Lisp.
Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by barrybe on Tuesday November 29, 2011 @01:33PM (#3291518)
Wait.. why is raganwald replying to raganwald?
Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by raganwald on Tuesday November 29, 2011 @01:48PM (#3291591)
He’s meta-circularly tail-calling himself out.
Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by akkartik on Tuesday November 29, 2011 @01:52PM (#3291608)
I looked up Nicolai Bourbaki -- and then I got the joke :)
Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by jes5199 on Tuesday November 29, 2011 @12:11PM (#3291110)
I didn't claim it was revolutionary, I just keep hearing LISP hackers say "there's no reason to care about XML or JSON if you've got S-Expressions, which are so much cleaner"

This project is exercising (proving? refuting?) that claim. I recognize that this isn't the most ambitious project in the world, but it was a Thanksgiving-weekend hack.

I'm thrilled that it got the 20 votes necessary to get it on the front page of HN.

Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by lisper on Tuesday November 29, 2011 @12:19PM (#3291148)
I vote for "prove". All those extra and unnecessary quotes and commas. Blech. And all that extra ugliness just so you can re-use the JS parser? IMHO there's no excuse for this. It's really easy to write a parser that does the Right Thing, e.g.:

http://www.flownet.com/ron/lisp/l.py

Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by apotheon on Tuesday November 29, 2011 @01:14PM (#3291407)
I think the "any interesting feature" in this case is the fact it uses JSON rather than s-expressions. This may not be a feature you think it needs, but it's interesting nonetheless.
Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by xyzzyz on Tuesday November 29, 2011 @04:18PM (#3292217)
It still uses S-expressions, albeit with different kind of parentheses and separators. The whole point of S-expressions is that syntax is irrelevant.
Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by yangyang on Tuesday November 29, 2011 @12:11PM (#3291109)
Because it's pretty straightforward - there's very little parsing involved (in this case basically none).
Re:Show HN: a Lisp that uses JSON instead of S-expressions (... by lisper on Tuesday November 29, 2011 @12:32PM (#3291207)
No, there's a lot of parsing happening. It's just that you're using (part of) the Javascript parser to do it.