So there is nothing like a demo with unusually terse examples to unearth issues. I created a dorky little style formula that returned {:color :red} and had no dynamic dependencies so it got optimized away. Glad I did! Turns out the implementation of cf-freeze , a new feature that would let a formula sign off further calculation, broke the cell optimization scheme.
Had fun getting deep into MX internals again, and I did start building out an MX "tracing" facility that was quite handy in debugging the problem. This might not be sth an MX user will ever need -- I really want to make MX and W/MX dev friendly with proactive error detection -- but it will be there as an option.
With that out of the way, my personal roadmap is:
• dress up async MX formulas so no async mechanism is assumed;
• announce MX 5.0.0;
• start on the W/MX Inspector, keeping an eye out for any other issues I may have introduced lately. This will also be structured as a pedagogical device, so noobs have sth to learn from; and
• when W/MX looks solid, announce that and invite folks to work through the inspector material.