I said "does", not "has". True, newLISP, by design, lacks many of Guile's language features. But when it comes to buckling down and getting stuff done, newLISP does indeed "do" anything that Guile can do. Often much more simply.
Compilers? Who needs them. We have a linker that can create a "binary" blob that you can drop in place and run. Close enough.
Multi method dispatch? Our OO system (FOOP) does what we need it to. OO is an often over-used and overrated paradigm.
Hygeinic macros? They just tie you down. Yuck. First class and composable continuations? If you need them, you can implement them in a few lines of newLISP. Most people don't.
Full numeric tower? We use the Gnu GMP library when we need big numbers. Otherwise, we keep it close to the machine, just like C. floats and ints and chars. Saves cpu cycles, and let's me enjoy all the bit-banging fun I had back in my Assembly programming days.
Tail calls would be nice, but I really haven't missed them. The iteration primitives are well done, and tail calls can always be implemented with iteration, if speed turns out to be an issue.