News for hackers. Stuff that matters.
Re:On Leaky Abstractions and Objective-J by tolmasky on Monday December 08, 2008 @02:32PM (#390231)
There is also the issue that implementing things like method_missing and import are prohibitively difficult without new syntax.

Objective-J's code importer is one of the more complex pieces (as it manages to do so completely asynchronously). All the approaches that use a simple JavaScript function to grab code, like grab_and_eval("file.js") are forced to happen synchronously (since you have to guarantee that the code is evaled before the next line). Without some sort of lexing support, its really not possible to both grab files asynchronously and also be able to continue executing.

Also, as stated in the article, you can't intercept JavaScript method calls, so if you want something like method missing you're forced to do something like:

call_method_or_send_method_missing(object, "method_name")

And again, since Objective-J is a proper superset of JavaScript, it doesn't lose any of its powerful features.

Re:On Leaky Abstractions and Objective-J by drwh0 on Monday December 08, 2008 @02:42PM (#390252)
And again, since Objective-J is a proper superset of JavaScript

really? what can it do that js can't do?

Re:On Leaky Abstractions and Objective-J by docmach on Monday December 08, 2008 @02:51PM (#390273)
Being a superset of JavaScript doesn't mean it can do more, it just means that all valid JavaScript is valid Objective-J.
Re:On Leaky Abstractions and Objective-J by jorgeortiz85 on Monday December 08, 2008 @02:51PM (#390269)
Read his first sentence again:

"There is also the issue that implementing things like method_missing and import are prohibitively difficult without new syntax."

Re:On Leaky Abstractions and Objective-J by drwh0 on Monday December 08, 2008 @04:07PM (#390377)
"difficult" has nothing to do with the power of languages

TeX macros are fundamentally as expressive as java.