> have one dependency that hasn't been updated to support Core and you can't upgrade and then you can't use anything new. That's not true. Friction in tooling

> have one dependency that hasn't been updated to support Core and you can't upgrade and then you can't use anything new. That's not true. Friction in tooling and project description files does not really equate to instability for production use - "worth it" is quite subjective and also not equatable to stable. As you said, Core v2 was already out 2 years ago, and plenty of people were using Core v1.X in production on significant sites without much trouble.