85% bigger parser size compared to pegjs optimized for size

[NogaMan]

I've seen the optimize option was removed, but maybe it should be restored?
When i tried using peggy instead of pegjs in my project, the generated parser size increased almost 2 times.

The test was done by building the generated parser with webpack with minify option, so you might expect such increase in a production build.

Initially I've tried to migrate from unsupported old library but currently don't see any benefits, as this issue and bad TS typing exist.

[hildjj]

We tested this before making the change to remove size-optimized parsers, and found that all of the grammars we tested generated larger output with the size optimization on. If you have grammars that benefit from that optimization, can you please link to them?

[NogaMan]

https://github.com/pegjs/pegjs/blob/master/examples/javascript.pegjs

[th0r]

We also have a parser based on javascript.pegjs which supports only subset of the language and the numbers are the following:

Output size	Unminified size	Minified size
PegJS (--optimize size)	31.84kb	14.9kb
Peggy	112.68kb (+254%)	28.63kb (+92%)

For the original javascript.pegjs the minified numbers are not so dramatic, but still noticeably higher:

Output size	Unminified size	Minified size
PegJS (--optimize size)	105.5kb	63kb
Peggy	281.3kb (+166%)	76.8kb (+22%)

Will it be possible to bring back the --optimize size option?

[hildjj]

I'm open to a patch that adds back the size optimization, but I'm unlikely to do the work myself. Perhaps @Mingun has a patch handy and could be talked into working on it.

[Mingun]

No, I doesn't have one and I'm not interested in it. In my opinion, compressed zipped version of script will have comparable size with th old optimized-for-size parser. I believe that browsers can handle compressed resources automatically.