J-expressions make Javascript the acceptable Lisp

The consistent implementation of key enumeration order of objects in Javascript engines allows us to write specifications of composeable computations using generic JSON-serializable notation that we can call “J-expressions”.

{opname: main_parameter,
keyword1: value1,
keyword2: value2,
...}

J-expressions, in combination with functions that implement what the operation named opname is supposed to do, are then a systematic way to approach DSL construction within Javascript. The notation is as expressive as s-expressions.

>>37
You don't understand it because your mind has been conditioned and formed by the statically-typed COP languages.

self-contained objects that communicate to one another by passing messages

What if you need to add functionality to existing objects, what do you do? Stop the runtime, edit code, recompile and run it again? That's not the OOP way. The OOP way is to never stop the runtime (save it to an image if you need), adding new message handlers or modifying old ones on live objects. This makes for rapid prototyping and fast code evolution. COP on the other hand is a poor man's OOP because defining object blueprints (aka classes) statically supposedly allows the compiler to optimize calls better.