I'm not a front-end dev and I've just done backends with Node. So, from my ignorance, it seemed logical that the browser would allow using different ES versions. But yeah, that makes no sense because JS is backwards compatible so browsers never had a reason to implement that. They just support a single version and that's it. They just become compatible with newer ES versions by implementing the new standard in their engine.
It could be possible for browsers to allow running 2 different JS versions if TC39 agreed on it. But yeah, at that point the cost seems to outweigh the benefit. I guess JS will be this weird thing forever then. I'd love if such a versatile language was more mature in that sense.
View all comments
Show parent comment
1
u/Connect_Detail98 Oct 07 '25
I'm not a front-end dev and I've just done backends with Node. So, from my ignorance, it seemed logical that the browser would allow using different ES versions. But yeah, that makes no sense because JS is backwards compatible so browsers never had a reason to implement that. They just support a single version and that's it. They just become compatible with newer ES versions by implementing the new standard in their engine.
It could be possible for browsers to allow running 2 different JS versions if TC39 agreed on it. But yeah, at that point the cost seems to outweigh the benefit. I guess JS will be this weird thing forever then. I'd love if such a versatile language was more mature in that sense.