I think dismissing a tool for its age/maturity requires a very specific use case; you must be starting a project now that you know will be very long lived. The

I think dismissing a tool for its age/maturity requires a very specific use case; you must be starting a project now that you know will be very long lived. The web is great because we have an insane amount of backwards compatibility. Old Wordpress sites and even geocities are proof of that. Those sites use pretty old browser tech but they still work. The technology behind alpine will still work identically in 10 years (assuming browser tech stays on the same course it’s been following for 30 years). If you’re building a one off blog or a brochure site that’s a one and done project, then who cares how old the tech is? (Within reason and scope etc). You won’t be coming back to that project ever again. I would argue that the case for maturity as a deciding factor, requires that your project live long enough to potentially need further support or features only made possible due to the extended investment into the framework. TL;DR: small apps can use whatever you want because they’re small.