That's the most fundamental one, plus the lack of expression based syntax (!), macros, quoting, (truly) interactive development...
It seems to me that there isn't much there outside of proper closures and data literals? Go has those as well and it's hard to compare to a Lisp.
When JS was invented it was inspired by Scheme and apparently having those two features was more out of the ordinary then. But that's hardly true today.
But there is a _qualitative_ difference between interactive development between JS and a Lisp like Clojure. And "pretty much" is also qualitatively less expressive than "everything is an expression".
I write expression based, simple, mostly functional JS and I use tools to make that as interactive as is practical. But there's still a lot of friction and differences between that and development with a Lisp (in my case Clojure).
The entire Javascript language is not striclty homoiconic, then again many lisps aren't if you're exceedingly hawkish about that term, but the "code is data" mentality is obviously present in the way Javascript and JSON interact.
It seems to me that there isn't much there outside of proper closures and data literals? Go has those as well and it's hard to compare to a Lisp.
When JS was invented it was inspired by Scheme and apparently having those two features was more out of the ordinary then. But that's hardly true today.