4 ms·

Unfortunately, I didn't see improved documentation in their future vision... I'm not sure how a lot of those ideas will work with compatibility with older vers

by JDDunn9 13y ago

Unfortunately, I didn't see improved documentation in their future vision... I'm not sure how a lot of those ideas will work with compatibility with older versions of IE. You already have issues using the element tags for new attributes.

palmer 13y ago
You can get around the IE problem by using classes to call your directives rather than element tags. <div class="ng-view"></div> isn't as pretty, but it works in IE8. http://docs.angularjs.org/guide/ie http://docs.angularjs.org/guide/ie Agree that the documentation is still lacking.
- yoshokatana 13y ago
  Attributes also work for directives, though I like using ng-cloak as a class. I think in the future (next year, when my company will probably drop ie8 support) I'll start using custom tags.
teleclimber 13y ago
There is a limit to how long developers will support these old browsers, even if they sell to corporations and institutions with backwards IT policies. Some companies and even healthcare institutions are seeing the light and upgrading their systems. As more and more do, it makes less and less business sense to support old browsers (fewer companies still using them, and it only gets harder to make a modern web-app work on them). There is a huge cost to supporting old browsers. There IS a tipping point where it's just not worth it anymore. So the companies/institutions that don't upgrade will soon enough be left behind. That's just the way it is.
saidajigumi 13y ago
If you must support outdated versions of IE then your future is grim. The working tools you have today are all you will ever get. An expectation for ongoing framework support for these legacy environments is wholly unrealistic.
- JDDunn9 13y ago
  I hate IE compatibility too, but there's still a lot of people using them; ~5% use IE8, ~2 use IE7. What business is willing to give up 7% of their revenue?
  - ceejayoz 13y ago
    I'll happily give up 7% of revenue if I spend more supporting that small subset's outdated tech than I make in profit off them...
    - rhizome 13y ago
      Give up 7% of revenue to speed up development by 30%.
  - lucisferre 13y ago
    Depends on a few more things: 1) If it's actually 7% of your revenue as opposed to just global traffic stats. 2) If entrenched IE customers would actually stop using your product rather than just install another browser. 3) If the cost of maintaining shims, backwards compatibility and ultimately just falling behind the competition in both experience and features is less than that potential 7% market.
    - markkanof 13y ago
      And to expand on your points, is there anyone that is an entrenched IE 7 or 8 user because they just love that browser. My guess would be not, and that instead they are just using that because it's the latest version of IE that they can get on their OS. Anecdotally, I've seen a number of large organizations that I work with allow installation of new third party browsers even though they stay at an old version of IE for compatibility reasons. So my point is that of that 7% that are using older versions of IE, it's probably a much smaller number that would not be willing or able to use an alternate browser to run your web application if they find value in it.
  - rhizome 13y ago
hmottestad 13y ago
hahaha. Did you ust say "compatibility with older versions of IE". I'll probably get downvoted for this but. If you want to maintain "compatibility with older versions of IE" try an older version of HTML, an older version of CSS, an older version of javascript and an older x86 processor, and an older version of windows (95 sounds nice). Sorry. If future features should try to remain compatible with older versions of IE we will get very little innovation.
- teleclimber 13y ago
  downvoted? No, you're totally right. We need to move on. see my rant below. upvoted.
  - stretchwithme 13y ago
    I know. Browsers are free. What's the hold up? Of course, its those creaky old IT departments. Stop catering to these old browsers and people who want your app will download a capable browser or pressure their IT or just use their phone.
    - stretchwithme 13y ago
      Maybe what we need is a general strike. Have every app go dark for these old browsers on January 1st 2014 for one hour a day. Then double it every day until its 24/7. If they can deal with Y2K, they can deal with something this trivial.
    - mindcrime 13y ago
      Ah yes, the "creaky old IT department"... Gosh darn it, if it weren't for those old fogies and their weird inclination to worry about making sure things actually work, and their bizarre insistence of mapping technological choices to the strategic concerns of the business (as opposed to just providing the coolest new toys for all the geeks to play with) - then, we might actually be able to get something done!
      - 13y ago

by JDDunn9 13y ago

palmer 13y ago

You can get around the IE problem by using classes to call your directives rather than element tags. <div class="ng-view"></div> isn't as pretty, but it works in IE8. http://docs.angularjs.org/guide/ie http://docs.angularjs.org/guide/ie Agree that the documentation is still lacking.

yoshokatana 13y ago
Attributes also work for directives, though I like using ng-cloak as a class. I think in the future (next year, when my company will probably drop ie8 support) I'll start using custom tags.

teleclimber 13y ago

There is a limit to how long developers will support these old browsers, even if they sell to corporations and institutions with backwards IT policies. Some companies and even healthcare institutions are seeing the light and upgrading their systems. As more and more do, it makes less and less business sense to support old browsers (fewer companies still using them, and it only gets harder to make a modern web-app work on them). There is a huge cost to supporting old browsers. There IS a tipping point where it's just not worth it anymore. So the companies/institutions that don't upgrade will soon enough be left behind. That's just the way it is.

saidajigumi 13y ago

If you must support outdated versions of IE then your future is grim. The working tools you have today are all you will ever get. An expectation for ongoing framework support for these legacy environments is wholly unrealistic.

JDDunn9 13y ago
I hate IE compatibility too, but there's still a lot of people using them; ~5% use IE8, ~2 use IE7. What business is willing to give up 7% of their revenue?
- ceejayoz 13y ago
  I'll happily give up 7% of revenue if I spend more supporting that small subset's outdated tech than I make in profit off them...
  - rhizome 13y ago
    Give up 7% of revenue to speed up development by 30%.
- lucisferre 13y ago
  Depends on a few more things: 1) If it's actually 7% of your revenue as opposed to just global traffic stats. 2) If entrenched IE customers would actually stop using your product rather than just install another browser. 3) If the cost of maintaining shims, backwards compatibility and ultimately just falling behind the competition in both experience and features is less than that potential 7% market.
  - markkanof 13y ago
    And to expand on your points, is there anyone that is an entrenched IE 7 or 8 user because they just love that browser. My guess would be not, and that instead they are just using that because it's the latest version of IE that they can get on their OS. Anecdotally, I've seen a number of large organizations that I work with allow installation of new third party browsers even though they stay at an old version of IE for compatibility reasons. So my point is that of that 7% that are using older versions of IE, it's probably a much smaller number that would not be willing or able to use an alternate browser to run your web application if they find value in it.
- rhizome 13y ago

hmottestad 13y ago

hahaha. Did you ust say "compatibility with older versions of IE". I'll probably get downvoted for this but. If you want to maintain "compatibility with older versions of IE" try an older version of HTML, an older version of CSS, an older version of javascript and an older x86 processor, and an older version of windows (95 sounds nice). Sorry. If future features should try to remain compatible with older versions of IE we will get very little innovation.

teleclimber 13y ago
downvoted? No, you're totally right. We need to move on. see my rant below. upvoted.
- stretchwithme 13y ago
  I know. Browsers are free. What's the hold up? Of course, its those creaky old IT departments. Stop catering to these old browsers and people who want your app will download a capable browser or pressure their IT or just use their phone.
  - stretchwithme 13y ago
    Maybe what we need is a general strike. Have every app go dark for these old browsers on January 1st 2014 for one hour a day. Then double it every day until its 24/7. If they can deal with Y2K, they can deal with something this trivial.
  - mindcrime 13y ago
    Ah yes, the "creaky old IT department"... Gosh darn it, if it weren't for those old fogies and their weird inclination to worry about making sure things actually work, and their bizarre insistence of mapping technological choices to the strategic concerns of the business (as opposed to just providing the coolest new toys for all the geeks to play with) - then, we might actually be able to get something done!
    - 13y ago