While I understand that feeling, I've come to realize it's an inevitability, that shouldn't affect your work.
At any given time, you either have a need/problem, or you don't. If you DO, you evaluate the current tech available, and hopefully select something that fits your needs. You build out around said tech, and if your choice was correct, that means it's either solving your problem, or on it's way to.
If something comes along while you're implementing with your chosen solution, that looks similar, but better, it's only noise - because hey, you found a solution.
Just as we don't all re-write all of our code whenever a new language comes along (unless the thing in question was desperately in need of a re-write anyway) even if newer languages are nicer, we needn't switch DBs or frameworks for the same reasons.
Comments
While I understand that feeling, I've come to realize it's an inevitability, that shouldn't affect your work.
At any given time, you either have a need/problem, or you don't. If you DO, you evaluate the current tech available, and hopefully select something that fits your needs. You build out around said tech, and if your choice was correct, that means it's either solving your problem, or on it's way to.
If something comes along while you're implementing with your chosen solution, that looks similar, but better, it's only noise - because hey, you found a solution.
Just as we don't all re-write all of our code whenever a new language comes along (unless the thing in question was desperately in need of a re-write anyway) even if newer languages are nicer, we needn't switch DBs or frameworks for the same reasons.