How many times does it happen that devs leave an old job to go to a "prestigious" new job only to end up hating it?
In my case I don't like my new job and don't want to go back to my old job(even if I did kind of like what I did there). I'm kinda stuck waiting for a certain minimum amount of time to pass so that I could go to some other company doing work that I actually like doing.

What is it you don't like?

Well I certainly advocate for looking for better options and expanding your horizons but tbh unless you are your own boss most jobs will have something you dislike about them. Now that I think about it, even CEOs come to hate their jobs at some point, except Hugh Heffner he lived and died in bliss.

@Codex404 Old tech, client-centredness, being just one cog out of thousands...

@cst1992 the first thing can be tackled by discussing it.
The second thing makes sense. Its a company, customer is king.
Last one I can understand.

@Codex404 Tech is locked in; it's a big application and can't change. Thank God I am not working on the older version of their application; it was written in Flex(?!)

@cst1992 when new parts are written they can be written in newer or better tech. Slowly the application will get shaped to the new tech completely.

Look for example at gitlab. Their server code base consists of three languages because they are currently going though the same process.
If you can find good arguments you can at least try.
In Dutch we have the saying "Niet geschoten, altijd mis" which literally translates to "didn't shoot always a miss". Basically if you don't try you will never reach your goal, if you try you have a slim chance they say: let's try it out.