> const does not imply any kind of immutability of the value itself, it only implies immutability of the binding.
So you expected that `const` did the same work as `Object.freeze`?
Since in the post he never mentions Object.freeze, maybe he doesn't know about it?
And here is yet another developer having hard time understanding the difference between references and values.
Putting f**ks around statements of common knowledge and ranting doesn't make anything entertaining.
I'm pretty sure he understands the difference... he's just saying that if it doesn't make the object immutable then it is not that useful.
(I disagree with him. I think minimal variables reassigning makes code easier to understand and 'const' helps to encourage that)
But he thinks that is not intuitive. It is intuitive as f**k is all I'm saying. It sounds ridiculous when you make something that fundamental as a base for your rant.
"So you wake up every day and think that you can go on forever? NOPE! We all die in the end! F* that sh**!!"
I totally agree with the general feeling of the article, and I like the suggestion to only allow const / disallow let at the top level
I find that I often write a function which manipulates, say, an array with push or shift. Then I want to change the algorithm to use concat - oh wait I have to change `const arr = ...` to `let arr = ...`, because that's how concat works. It seems ridiculous
Honestly, I was ready to disagree with him but everything he said is (probably) true. I think it might have been easier to read if he presented his main point upfront: don't set up linters to cry fowl when using let instead of const or automatically convert to const.