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.

>>16
Because it's pointless syntactic sugar that bloats up every JavaScript parser, interpreter, and compiler that supports it.

What's the point in adding a totally different syntax for already existing things to an existing language?

JavaScript already has a lambda syntax (function). It already has a way to include the result of an expression in strings (the + operator). It has array indexing and a slice method.

They should have deprecated and froze JavaScript, and put the new features and syntax into a new language.

This type of superfluous syntactic sugar is introduced to pander to stupid people who don't see the forest for the trees. They think that making one thing easier is always good for the language as a whole, not understanding that making one thing easier may make other things harder.