[amedvednikov]

And you link to the very same thread by another language author that claimed there's no way V could be built in V and JSON decoding is impossible without an AST.

> Claims to "being able to now compile itself in 0.09 seconds" whilst pushing the need for an AST to the side represents a serious problem in the language's general direction

Critique for focusing on fast compilation times? :)

Any valid criticism?

[hybrids]

Are you advocating for implementing langauges in an AST-less way or are you working towards maturing your language? You don't sound diametrically opposed to ASTs (which are evident in essentially any modern language), so I have to ask why V was not originally implemented with one and why you don't consider it a more important problem.

Using codegen to handle the JSON stuff is clever, sure, but it certainly makes me uneasy! It gives a very Jenga Tower impression of the state of the project...

[tastroder]

> Using codegen to handle the JSON stuff is clever, sure, but it certainly makes me uneasy!

Why? That thread seems to talk about this in the context of serialization and the way your parent poster is proposing is pretty common in the microprocessing world since dynamic parsing would be wasteful and, given fixed data structure, can be unnecessary in some cases.

Honestly, the most interesting thing to me as an outsider in that whole github issue you posted is how much mudslinging and animosity seems to be going around in the PL development community. It's not like people are forced to use alpha releases of random programming languages popping up on github.

[Yoric]

> You don't sound diametrically opposed to ASTs (which are evident in essentially any modern language)

Fwiw, I'm not sure what you mean by AST in the context, but if you're talking about an actual in-memory AST, there's (once again) research in getting rid of it for compilation.