Lars Marius Garshol

93% of the tests now pass. A good part of what remains is parsing, which is easily fixed. Transforms with own JSON representation is now marginally slower than with Jackson...

The motivation for dropping Jackson is that some users have dependencies (such as Spark) that require versions of Jackson that are incompatible with the version we have. That means we...

Letting the user supply the JSON parser and representation is a real no-no, because it's going to make adoption so much harder for users. We have to give them a...

I think everything you write here is totally fair. My plan is to make a version of JSLT which defines its own interfaces for the JSON representation. I also plan...

The templates are compiled. When you call `Parser.compileString` what you get back is a template that's fully parsed and ready to be executed. It's even been through an optimizer. So...

I will work on that, but it's a lot of work, and I think you'll find performance is pretty good already. I can run a large, complex transform at 150,000...

I agree, and I'm still planning to do it. But it will take a while.

A comment was added on this issue that seems to have disappeared. I guess the author deleted it. I thought it was worth bringing up, so I'll repeat the comment,...

Oh, I see. The literal `..` syntax would be turned into an array literal at compile time if the numbers are given as intervals. If they're not you do need...

Having `*` work with strings was deliberate. It's even used in the built-in example in the playground. :) But if it doesn't work with arrays we should fix that, agreed....