Do we have more clues as to what migrating an angularjs directive into a webcomponent will look like ?
This is my biggest fear with Angular
The Future of AngularJS
21–30 of 74 posts
Re: The Future of AngularJS
#22I was really excited when I saw the multiple responses possible for a given request
Re: The Future of AngularJS
#23Unfortunately, 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.
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.
Re: The Future of AngularJS
#24I was really excited when I saw the multiple responses possible for a given request
This does sound useful, but I'm not sure what it has to do with Angular. Are they going to create more resources with the assumption that HTTP 2.0 will fix it?
Re: The Future of AngularJS
#25What I don't understand is all the whining about posting slides. This is fresh off the presses, answers hot questions in the angular community, and obviously people are upvoting it. If you're aware of what's happenning in Angular, every slide stands on its own and has useful info. Can we please give all the moaning about format a rest please?
Yeah I don't understand it either. This is very much in line with cryptic style of communication by AngularJS :-)
Re: The Future of AngularJS
#26I hate choosing between Angular and Polymer.
Re: The Future of AngularJS
#27Unfortunately, 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.
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.
Re: The Future of AngularJS
#28What I don't understand is all the whining about posting slides. This is fresh off the presses, answers hot questions in the angular community, and obviously people are upvoting it. If you're aware of what's happenning in Angular, every slide stands on its own and has useful info. Can we please give all the moaning about format a rest please?
I 100% agree, I just started using AngularJS and I'm very happy to see a preview of what I'll have to learn in the future and how current practices will change.
Re: The Future of AngularJS
#29What I don't understand is all the whining about posting slides. This is fresh off the presses, answers hot questions in the angular community, and obviously people are upvoting it. If you're aware of what's happenning in Angular, every slide stands on its own and has useful info. Can we please give all the moaning about format a rest please?
I wouldn't call this fresh off the presses. The angular team talked about many of these points back in June. http://www.youtube.com/watch?v=W13qDdJDHp8
It's really exciting. This is a good summary of the future though.
Re: The Future of AngularJS
#30Unfortunately, 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.
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.