zephyrus-sc2-parser VS parse-rosetta-rs

This is insanely cool! Very impressed you managed to implement a full parser in Rust.

I implemented a basic one in Rust a while back: https://github.com/ZephyrBlu/rust-parser

And a full one in Python with a few bells and whistles ages ago: https://github.com/ZephyrBlu/zephyrus-sc2-parser

Don't maintain either of them though :(, and the Rust one is super rough.

SC2 is a very interesting area for data analysis, but at the same time I found it very challenging. There is so much nuance and inconsistency across games it can be really hard to do accurately do things like categorize builds or measure build timings.

The area I ended up focusing on was builds, and I feel like I did some interesting stuff there: https://sc2.gg/reports/top-openings-2022/.

I found personal statistics less interesting than aggregate statistics. Even pro games are very volatile, ladder games even more so. Extremely hard to get reliable signal out of them if you're trying to track things across games. Even simple things like Collection Rate are poor indicators without significant categorization work (Matchup, build, opponent build, etc).

There is the sc2reader parser which has been around for a while, and I also have a Python parser.

Check out this guy's work, he tracks a lot of details. https://app.zephyrus.gg/login https://github.com/ZephyrBlu/zephyrus-sc2-parser

This is one of the projects I've been working on for over a year: https://github.com/ZephyrBlu/zephyrus-sc2-parser.

I love analyzing SC2. I wrote my own replay parser, I created a replay analysis site (FYI this is an old video) and I regularly post graphics of stats/analyses such as:

This is the parser: https://github.com/ZephyrBlu/zephyrus-sc2-parser

Comparing performance of parser libraries

For a very rough comparison of parsers, see https://github.com/rosetta-rs/parse-rosetta-rs

Since this takes a unique approach, would you be interested in adding it to parse-rosetta-rs? Its a repo to help users do a comparative analysis of parser crates, providing some very crude stats to help get them started and allowing them to compare what the APIs look like.

The reason I assume its unrelated to combine is that for the json implementation, a previous version of combine built in about the same time as nom

I'm tempted to collect all of these benchmark repos into a github org to make them easier to find. So far I know of parser, md, argparse, and template languages.