*If programming can be described as "making programs", metaprogramming could be ...

AdieuToLogic · on June 27, 2015

If I could up-vote recursively until the Inter-tubes segfaulted, I would on that link you provided.

A couple quotable lines from the article I have to throw out there are:

> One day, Netscape woke up from a truly epic bender to discover it had jammed a scripting language onto the web and millions of people were using it. Literally none of them liked it. Not one.

> Lots of programmers believe JavaScript is “basically” Scheme because it gives them something they want to believe: that the language they choose to use has some cachet and they don’t have to feel bad about it anymore.

jstuxx · on June 27, 2015

Lots of languages claim they are Scheme or Lisp dialects (JavaScript, Python, Ruby, Lua and others) in order to boost their popularity even though they have none of Lisp's unique features but just the general features you would expect to find in any dynamically typed languages.

Retra · on June 27, 2015

Python claims it's a Scheme/Lisp dialect? Where?

financequoll · on June 27, 2015

I think that link needs a bit of updating - JS has lexical scoping and tail call elimination now.

epidemian · on June 27, 2015

> JS has [...] tail call elimination now.

In a very narrow hay of "has", as in "ES2015 the spec has it, but no JS runtime implements it yet": http://kangax.github.io/compat-table/es6/#proper_tail_calls_...

I'm not trying to be a contrarian. It's just that i see lots of JS developers excited about superfluous things like class syntax or symbols, whereas real game changing additions like proper tail calls seem to pass by unnoticed, and unimplemented by JS runtimes :(

current_call · on June 27, 2015

I tried to create an infinite loop in Firefox and got a "InternalError: too much recursion". Then when I tried it in Chrome I got "Uncaught RangeError: Maximum call stack size exceeded".

function x() { return x(); }

Kiro · on June 27, 2015

I think you misunderstood "now". It's "now" as in ES6/ES2015, not ES5 which the browsers are running by default.

financequoll · on June 27, 2015

That's still expected?

current_call · on June 27, 2015

It's a recursive tail call. It should run forever, like the following Scheme code.

(define (foo) (foo))

(foo)

financequoll · on June 27, 2015

Ah, right, yes I get what you mean.

The main problem is still that Chrome and Firefox don't support tail call elimination. Babel (6to5) and Traceur do.

strmpnk · on June 27, 2015

They don't. They support an optimization for self recursive calls but not general tail call elimination.