I cope by only using tech that has been battle tested, solves a problem and proven to last for a long time to come. Most people still use REST APIs. GraphQL is

I cope by only using tech that has been battle tested, solves a problem and proven to last for a long time to come. Most people still use REST APIs. GraphQL is cool, sure. But it solves a very particular problem. Why use it if you don't need it? Same goes for old standards like SOAP. If it still works then no point in changing it. They all do pretty much the same thing anyway. I've not even heard of trpc. goes and check. It's only 2 years old, that's why. What problem does it even solve? Types? We have OpenAPI for that. From what I can see, new tech only become mainstream if it solves a problem. trpc may make things nicer to use, but since it doesn't solve a problem that's not already solved, it'll probably never get big enough to be mainstream. Compare this to Typescript. Its first version was 2012. I started using it around 2019. 7 years after it was released. Was it doing something new? No. It's bringing static type checking to JS. In fact, I would argue that it makes the language feels more similar to existing languages like C# and Java. Did it solve a problem? Definitely. Many people want static type checking. And here we are in a Typescript world. Same goes with SSR/SSG, hydration, routing, etc. They solve a very particular problem. If you don't have that problem, no point in using it. Most websites still uses PHP and work just fine.