Pushing something onto an array isn't changing the array? It's not changing the reference to the array, but from a style standpoint it doesn't make sense.

And if you're declaring a const within the scope of a function, it's still allocating memory when it enters the scope and disposing it when it leaves the scope, same as a variable. There's no performance benefit to do this.

Something like const CONSTANT_VALUE = "This never changes" has a performance benefit and is actually how other languages use constants. The value will always be the same, the compiler understands this and can optimize accordingly. If you're declaring an iterator or the result of calling a webservice to be const it'll be a different value every time it runs that code, so it's not something a compiler can optimize. In style terms, it's a value that's different every time you get to that line of code, so why would you want to call it constant?

You're comment indicates the FE dev obsession with always using const stems from a misunderstanding of how computers work. But of course many religious beliefs originate from a misunderstanding of the world. Whatever man, I just make it a const to make the linter happy, because it's dumb FE bullshit LOL.