Accounting thing in the sense that those are expenses that have not been paid in cash, but with options for the future Anthropic shares.
So they might not be very relevant for the solvency of Anthropic, but that means that if their IPO flops they will also pull down others with them.
Regardless how they have paid for them, the expenses of Anthropic remain many times greater than their revenues. By accepting to not be paid now, their creditors are also gambling on their future success.
Yea, looks like it (at least for their v2). Fable did much better in V1, but once they added their tooling around it, Opus + Composer ended up doing better (>0.8 Grade on the SQLite chart) for the final product. Granted, Fable reached a 'good' result (0.7~) in a much faster timeframe.
Point is, frontier models don't necessarily are better than a swarm of non-frontier ones for these scoped problems. IMO frotnier models excel at underspec'd or more complex problems where ideation and exploration are key (and that's where they become crazy expensive).
Anthropic wants it that way so they can’t be sued… the correct answer is don’t, switch to Kimi K3 for much more usage, the same quality of model, and no hidden practices :/
Whether or not this is useful (I am also not sure), the JSON doesn't need to survive into runtime at all. If you include the JSON, do a bunch of `if constexpr`, and never touch the JSON outside of a constexpr context, it doesn't have to any footprint on your binary. (I'm not sure if #embed will force stuff to stay in your binary even if you never reference it at runtime)
You're right to point out that this is really 'first class JSON', rather than the Pydantic/Jackson type thing where the json barely exists and is immediately transformed into your models and classes.
Thanks for reading the article though, that's cool. I am a daw_json_link fan
Build up the test suite inside static asserts, or a macro that lets you switch. It will be really nice when you update right and your IDE will tell you before you even hit compile because clangd found an issue.
