Echo JS 0.11.0

<~>

MaxArt 2770 days ago. link 1 point
"The two latter work with IE6+, which is a big advantage nowadays."

This is why we can't have nice things.

If you're to develop a web application for the modern world, let the users get a browser worth of a web application. Still giving support to IE6 in 2016 is what kept web development back for so long.
gotofritz 2769 days ago. link 4 points
Sadly in the corporate world it doesn't work like that. In finance and banking, which are audiences likely to use graphs, you can find a lot of obsolete browsers.
MaxArt 2768 days ago. link 1 point
My point still stands. The problem is with commissioners who don't understand that keeping your software outdated leads only to sub-optimal experience and/or extended development times.
Installing Chrome or Firefox beside IE6 (if they *really* want to use some legacy ActiveX web app) is free, feasible, fast and just a one-time investment for the administrators.
This is why we, as developers, should try to convince them.
gotofritz 2767 days ago. link 1 point
You obviously have no experience of these environments. It's simply not feasible in certain organisations where IT is very tight and ultra conservative and FE developers are well at the bottom of the food chain.
MaxArt 2767 days ago. link 1 point
I actually had plenty of experience with that type of clients, sadly. I've never gone back to IE6 fortunately, but I have with IE7, and that felt terribly outdated right back then.
Oh, sure, Microsoft was still releasing security patches. They could hide behind that. But now it doesn't, and keeping your software outdated, in the bliss of a false sense of security, is plain stupid.
The point is: stop working for them. You already know that you're not going to get anything good from such clients, and you'll find yourself regretting of not having asked for more money.