Have you had the same experience? How much time did you spend on this problem in the last week? What tools do you use to guide your decisions?
For things that are doing a decent job, I basically don't even consider replacing them. If something in the space seems to be picking up a heap of momentum, I'll make a note of it to investigate next time a project starts. More often than not, the hype has moved on by the time I get there, and I saved myself a bunch of effort.
For things that are an active point of pain, I keep a closer eye on alternatives. Mostly just keeping a rough mental list of what's becoming popular, and what their purported advantages are. At some point, I'll usually do a little toy project using one or two of them, just to see how they really work in practice.
So, eg. I've been using PostgreSQL since the late 90's. Pretty early on I chose it over MySQL, and I've been pretty happy with that outcome. I played with Mongo a bit, but ended up sticking with Postgres' JSON datatypes when I want a document model. OTOH, I have adopted Sqlite3 for things where it makes sense, and I'm still keeping an eye on time-series / columnar database alternatives.
I picked Python very early (I first used it pre 1.0, and had production apps using 1.1) and still use it a heap today. I've played with Go a bit, and in the right projects, I'd probably use it today, although the messing with generics encourages me to wait a little longer. I moved to Python3 with v3.7.
Knowing something well, and being very productive with it, counts for a lot. Stable, well-supported, well-known things are much better components of a stack than something that looks shiny, but is obsolete in a year or two. If something is good, it'll be around long enough that you can pick up it next time.