I understand the feeling, but they probably didn't do it this way to avoid breaking backwards compatibility. They should do it right from the beginning.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
@pamelafox I’m so sorry! @wycats warned me const was a mistake for this exact reason and I didn’t take it seriously enough. One of my main ES6 regrets.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
I understand the feeling, but they probably didn't do it this way to avoid breaking backwards compatibility.
They should do it right from the beginning.Hindsight is 20/20
Far enough.
That was an unhappy statement, at least I learned a new word. thanks 😬
Not saying you're wrong, just that it's not trivial :)
Ahh 2020 the only year I can make jokes about my vision.
Nowdays even
constis considered as a mistake 😅Constant complaining from the js community. 😆
Sadly a time machine written in early JavaScript probably wouldn't work very well 🥳 Merry Christmas