In the short term obviously yes, I can already feel myself veering away from new things that have @unstableAPIs. The framework designer may have to design for

In the short term obviously yes, I can already feel myself veering away from new things that have @unstableAPIs. The framework designer may have to design for users and LLM teachers this time. Designers should make it so logical jumps aren't to big like kotlin was back in the day and lagged in all code LLMs metrics until they made synthetic steps to "explain" it to the LLM. You can always add in the docs as RAG context later, maybe with an LLM synthetic booster explainer segment.