I'd like to just clarify one thing - of course everyone can ignore the new features when writing their code, but no one can ignore them when reading other people's code. Undoubtedly, a JS programmer must get a handle on them all, sooner or later.
Thanks for the es-discuss suggestion, it's cool that the process is open like that.
Understanding other people's code is never easy and I get that new language features make it seem even more daunting.
But it is always a useful process to go through, more so when it exposes you to new ideas, patterns and idioms. These features seem intimidating because they are unfamiliar to you, but they won't be unfamiliar forever. I guarantee it.
Wow, that was pretty patronizing! But I think I made a certain argument. You don't have to agree, but it would be nice if you don't just blame it all on my supposed unwillingness to learn new stuff ;)
Comments
I'd like to just clarify one thing - of course everyone can ignore the new features when writing their code, but no one can ignore them when reading other people's code. Undoubtedly, a JS programmer must get a handle on them all, sooner or later.
Thanks for the es-discuss suggestion, it's cool that the process is open like that.
Understanding other people's code is never easy and I get that new language features make it seem even more daunting.
But it is always a useful process to go through, more so when it exposes you to new ideas, patterns and idioms. These features seem intimidating because they are unfamiliar to you, but they won't be unfamiliar forever. I guarantee it.
Wow, that was pretty patronizing! But I think I made a certain argument. You don't have to agree, but it would be nice if you don't just blame it all on my supposed unwillingness to learn new stuff ;)