There is a particular confidence in choosing a familiar tool when a newer one would make a more interesting announcement.
Novelty has an operating cost
Every dependency brings documentation, updates, edge cases, and eventual replacement. A new capability can absolutely justify that cost, but the burden should be named before the tool becomes part of the foundation.
Boring can be generous
A well-known platform gives future editors, developers, and owners more ways to find help. Familiarity reduces the number of decisions that require a specialist and keeps routine work routine.
A boring foundation is often what gives the interesting part enough room to succeed.
Spend novelty carefully
Use the unusual tool where it creates a meaningful advantage. Keep the rest of the stack unsurprising. This concentrates experimentation in the part of the project where it can produce value instead of distributing risk everywhere.