You have to sign in with a Google account to access the content. All I get is a login page, at least. Anyone got a link that is publicly accessible?
The Future of AngularJS
31–40 of 74 posts
Re: The Future of AngularJS
#32Unfortunately, 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…
Re: The Future of AngularJS
#33Neato. Angular reimplementing it's own module system (when many developers already have a large body of code in existing module formats, particularly AMD) was one of the things that turned me off when first looking at it. Do ES6 modules have all the dependency injection stuff the Angular developers wanted?
Module system =/= Dependency injection.
AngularJS modules =/= CommonJS modules
Module system = way to FIND object definitions physically(files) or logically(name). Python has one, NodeJS has one.Dependency injection = way to WRITE objects by creating dependencies between them in order to separate concerns.
RequireJS = gives Javascript a module system
( fetching files according to the module name to
find module definitions ),which is
configurable since JS doesnt have one.
AngularJS = instanciate objects according to their
defintion and the definition of its dependencies =>
doesnt look for files in a path to find the definitons.
And ES6 definetly DOESNT DO dependency injection, ES6 gives JS a module system which is configurable.When ES6 gets it's module system , people wont need require JS anymore, but it has nothing to do with AngularJS.
Re: The Future of AngularJS
#34Is there a release schedule for ES6?
Re: The Future of AngularJS
#35Unfortunately, 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
#36Earlier quoted context omitted.
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.
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?
Re: The Future of AngularJS
#37Now whenever I see The Future of , I asume such thing is getting killed.
Re: The Future of AngularJS
#38Earlier quoted context omitted.
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.
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?
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.
Re: The Future of AngularJS
#39Earlier quoted context omitted.
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.
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?
Re: The Future of AngularJS
#40Earlier quoted context omitted.
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?
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...