Live data from Hacker News

The Future of AngularJS

docs.google.com

71–74 of 74 posts

Re: The Future of AngularJS

#71
post #68
post #61

Earlier quoted context omitted.

Please read posts before replying to them. - Nowhere in my post did I say a module system was dependency injection - Nowhere in my post did I say angular JS modules were CommonJS. Please don't use uppercase for emphasis, see http://ycombinator.com/newsguidelines.html Explaining in further detail: a feature of some module systems is dependency injection (yes, dependency injection can also be performed outside a module…

> - Nowhere in my post did I say a module system was dependency injection Let me remind you then: "Do ES6 modules have all the dependency injection stuff the Angular developers wanted?" > Explaining in further detail: a feature of some module systems is dependency injection An orthogonal, non relevant feature, that has nothing to do with the core role of a module system. That some module systems have this frankenstei…

The statement you are bizarrely quoting quite clearly does not equate dependency injection with module systems.

Again, read HN guidelines, your account is quite new and it's very obvious you haven't done so yet.

Re: The Future of AngularJS

#72

Earlier quoted context omitted.

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.

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!

Exactly. Use their need to make sure things actually work to get them to upgrade.

Re: The Future of AngularJS

#73
post #53

Am I the only one who thinks the name "Angular JS" is nonsensical and, frankly, a little silly?

I would guess it was originally "ng" for next generation, and then they wanted to come up with some kind of pronounceable name when they made it public. I'm just glad it's easy to google!

Re: The Future of AngularJS

#74
post #70

Earlier quoted context omitted.

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…

Well, the thing is both Chrome and Firefox get updated automatically but IE doesn't. So the problem will not IE versions that are already old (IE6, IE7) but current versions of IE - even future versions before they implement these new standards. As these features roll out to Firefox and Chrome, users of these browsers will have to them because of the auto-update pretty quickly. Eventually IE will implement them, mayb…

IIRC IE10 autoupdates
Post reply on HN