ES5 only at a possible job site. What do you think?

Question

JavaScript

ACHTUNG: a lot of letters and graphomania, lovers of concise questions urgently annihilate the tab!
Good afternoon guys! I’ll clarify right away - I’m not forcing anyone to make an important decision for me and I’m not trying to somehow naively transfer responsibility in such a matter to random people on the Internet. It's just curious to read the opinion of the experienced, tk. I have virtually no friends with whom I could chew this situation.
In general, the front-end, looking for the first job, today was at the next interview. According to the interview and the test as a whole, everything is tip-top, so there is a possibility that they will invite. By and large, I liked everything (workspace, people, conditions), but there is one depressing nuance - for various reasons, the company's internal tool, which will have to be actively used in work, was written a long time ago in ES5, which excludes the possibility of using ES6 + in general . And such forced work with ES5 can last indefinitely.
It would seem that the loss is small, since the syntactic magic, convenient methods (and other amenities) did not turn Javascript into another language, but, as I see it, regular practice on new standards fixes all modern techniques and approaches to writing code in the subcortex, which is crazy important for a novice developer at first. Especially if you take into account how rapidly JS is developing now.
Hence the question - what do you say? Am I right that this problem can become a serious dead end in development? Has anyone had this experience of using junk at work for a long time? Is it worth it to start?
If you managed to read to the end, I give you my love and I will tell my children about you.

Answer 1

I would generally prepare for the fact that at a new place of work (any) I won’t have to do what I like, but I’ll have to do what is boring, uninteresting, and possibly not at all on the stack. Approximately something like this:

Answer 2

Firstly, I don’t understand what “excludes the possibility of using ES6 + at all” means, no one canceled babel and polyfills, regardless of what the project was written on, another question is that this will also have to be configured in the project yourself.
Secondly, any first job gives a lot of experience, BUT the lack of experience with ES6 + greatly limits the possibility of getting a normal job in the future, for example, in our company we pay great attention to the experience with ES6 in interviews.
And thirdly, the experience of working only with ES5 in 2019 can give you more of an “anti” experience and a bunch of examples of how you don’t need to write code in 2019, so the benefits of such experience are doubtful in principle.

Answer 3

Definitely worth it. On the subcortex, put aside how javascript actually works. Prototypes, working with data and stuff like that. This will always be true.
And new features are learned quickly, from one evening to a couple of weeks.

Answer 4

You give too much importance to the programming language.
You still have to deal with very different things : patterns, concepts, algorithms, paradigms, principles, algorithms - and how to apply it all.
Language is secondary. He just learns.
Hard to learn - algorithms, paradigms, principles, concepts, patterns.
But! These things from language to language are passing.
PS:
As an example, you don't even understand yet that ES6 in its pure form is not applicable anywhere.
What transpilations are still needed for:
When you write in ES6, you run it through the transpiler - and you get ES5, which is laid out in the project.

Answer 5

I think for a career, the sooner you get experience in hype React, Angular, Vue frameworks, the easier it will be for you to present yourself at the next interview, it’s worth going to a company to support an internal legacy tool if the company or product is well known.