Good ideas are always relevant e.g backwards compatibility, minimalism, accessibility, simplicity in design. Technologies and fads may come and go.
JS is an interesting amalgamation of ideas. The primary one (portability) was to make the web more interactive, without having the user install a separate software. Java applets, Flash, ActiveX failed at this. JS allowed for web pages to go beyond simple text, images and hyperlinks. Most importantly, JS allowed a generation of programmers to play around with code in the comfort of their browsers, thus lowering the barrier to become a developer. Now that it has become ubiquitous, ECMA and major browsers do not deprecate parts of the language, leading to efforts like typescript, the (old) coffeescript and an increasingly complicated JS to smooth over old mistakes.
The support for IE is a battleground for ideas. Will you break the web for a section of your users who may not have control on their browsers due to IT policy? Or will you support a browser which has been abandoned by its vendor itself, knowing that users of that browser are at risk of viruses? Backwards compatibility vs security. As developers, we have to always fight conflicting tendencies of using shiny new technologies vs sticking to mature technology. Too much of the former leads to hype driven development where teams keep rewriting the product in framework du jour instead of solving business problems. Too much of the later may lead to security issues as the technology itself stops being maintained.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good ideas are always relevant e.g backwards compatibility, minimalism, accessibility, simplicity in design. Technologies and fads may come and go.
JS is an interesting amalgamation of ideas. The primary one (portability) was to make the web more interactive, without having the user install a separate software. Java applets, Flash, ActiveX failed at this. JS allowed for web pages to go beyond simple text, images and hyperlinks. Most importantly, JS allowed a generation of programmers to play around with code in the comfort of their browsers, thus lowering the barrier to become a developer. Now that it has become ubiquitous, ECMA and major browsers do not deprecate parts of the language, leading to efforts like typescript, the (old) coffeescript and an increasingly complicated JS to smooth over old mistakes.
The support for IE is a battleground for ideas. Will you break the web for a section of your users who may not have control on their browsers due to IT policy? Or will you support a browser which has been abandoned by its vendor itself, knowing that users of that browser are at risk of viruses? Backwards compatibility vs security. As developers, we have to always fight conflicting tendencies of using shiny new technologies vs sticking to mature technology. Too much of the former leads to hype driven development where teams keep rewriting the product in framework du jour instead of solving business problems. Too much of the later may lead to security issues as the technology itself stops being maintained.