zephyrus-sc2-parser VS Preact

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

In this post, we get to know more about Preact, one of this year's trending libraries. And we'll compare it to React to see which one suits better for our projects.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Those who want to develop a library that can be used by any other reactive framework. I often see SignalLike type that tries to subtype it.

https://github.com/preactjs/preact/blob/757746a915d186a90954...

The official Preact documentation.

At the very bottom of the image, there are 3 blocks that I chose to call application components. If you are building a cross-framework library, these can be built with whatever tools you want! Only catch is, all the tools you use to build it, will be needed by everyone consuming it. So choose wisely, and be mindful of how many kilobytes of third party code you will need in order to ship. In Schedule-X, I chose to use Preact. You will probably be fine with most lightweight virtual DOM libraries, and just like with frameworks there are a few to pick from.

>> React is not traditionally used for making games, but that's part of the fun and the challenge. R

> MS Flight Simulator cockpits are built with MSFS Avionics Framework which is React-like and MIT licensed:

https://github.com/microsoft/msfs-avionics-mirror/tree/main/...

preactjs may or may not be faster: https://preactjs.com/

Million.js is faster than preact, and lists a number of references under Acknowledgements: https://github.com/aidenybai/million#acknowledgments

https://million.dev/docs :

> We use a novel approach to the virtual DOM called the block virtual DOM. You can read more on what the block virtual DOM is with Virtual DOM: Back in Block and how we make it happen in React with Behind the block().*

React API reference > Components > Profiler:

DEV is a Rails monolith, which uses Preact in the front-end using islands architecture. The reason why I mention all this is that it's not a full-stack JavaScript application, and there is no state management library like Redux or Zustand in use. The data store, for the most part on the front end, is all data attributes.