I really dislike the trend of tech talks turning into stand-up comedy routines where 75% of slides must be a funny image that barely relates to the point the speaker is making at the time.
What I'd really like to see in AngularJS is some sort of asynchronous module system a la AMD. Doesn't have to be AMD, but some way to not have to load a whole app in memory at once. I thought I saw a design document that mentioned they were considering this for AngularJS 2.0, does anyone know more about it?
I do know that you can use requirejs, does anyone have any experience to share using requirejs and angularjs?
We use angular with RequireJS, though we don't (yet) load any Angular modules lazily because it is not supported by Angular. There are workarounds (like https://github.com/marcoslin/angularAMD) which I have no experience with. We do load external libs (like MathJax, which is comparatively huge) lazily where possible.
Our AMD modules are actually TypeScript modules that generate the AMD wrapper. Works great, and makes for a very clean and modular codebase. In the end, we use r.js to concat and minify most of it (everything except the lazily loaded libs) down to a single file. Including Angular templates, using https://www.npmjs.org/package/gulp-angular-templatecache which can output the templates as initialization scripts inside and AMD wrapper as well.
AngularJS is terrible choice for a front-end framework. It's just bizarre from top to bottom. Not everything needs two-way binding. Not all SPA's use nesting to compose their user interface! Why does ng-if create a new scope? Using attributes as control structures is plain dumb. Component re-use is difficult because of nesting as a central paradigm.
Javascript is a wonderfully expressive language. Unlike AngularJS, ReactJS let's you use this wonderful language to compose your application, not the foolishness of Angular's "modules", "factory", and "service". Even Dependency Injection is a foolish concept in a language like Javascript. Composition and wiring can be orchestrated through code, it doesn't need an intervening layer!
Javascript already has well-establish design patterns - it doesn't need AngularJS.
Right! The presentation showed some of those design documents in a picture in a slide. Are those documents available? That's exactly what I thought when I saw that slide, that I'd love to read those documents.
I hope AngularJS implements a virtual DOM, but I'm keen to transition to reactjs anyways, as I prefer assembling a program from many libraries instead of a monolithic framework
[+] [-] Touche|11 years ago|reply
[+] [-] twerquie|11 years ago|reply
[+] [-] paulhodge|11 years ago|reply
[+] [-] aikah|11 years ago|reply
[+] [-] craigching|11 years ago|reply
I do know that you can use requirejs, does anyone have any experience to share using requirejs and angularjs?
[+] [-] SanderMak|11 years ago|reply
Our AMD modules are actually TypeScript modules that generate the AMD wrapper. Works great, and makes for a very clean and modular codebase. In the end, we use r.js to concat and minify most of it (everything except the lazily loaded libs) down to a single file. Including Angular templates, using https://www.npmjs.org/package/gulp-angular-templatecache which can output the templates as initialization scripts inside and AMD wrapper as well.
[+] [-] kuni-toko-tachi|11 years ago|reply
Javascript is a wonderfully expressive language. Unlike AngularJS, ReactJS let's you use this wonderful language to compose your application, not the foolishness of Angular's "modules", "factory", and "service". Even Dependency Injection is a foolish concept in a language like Javascript. Composition and wiring can be orchestrated through code, it doesn't need an intervening layer!
Javascript already has well-establish design patterns - it doesn't need AngularJS.
[+] [-] digisign|11 years ago|reply
[+] [-] myliverhatesme|11 years ago|reply
[+] [-] craigching|11 years ago|reply
[+] [-] ionwake|11 years ago|reply
[+] [-] peterbraden|11 years ago|reply
Reactjs is simply the view layer, and plays nicely with other libraries.
[+] [-] acconrad|11 years ago|reply
[+] [-] NicoJuicy|11 years ago|reply
angularjs is mvc (Model View Controller)
react is only the V(iew), so you can blend AngularJS with ReactJS.
The most popular post (about Angular vs React) is on http://www.quora.com/Pete-Hunt/Posts/Facebooks-React-vs-Angu... , but it's kinda subjective i suppose as he works on the React team.
(Note: I use AngularJS, but haven't used ReactJS. So if i'm wrong, please correct me).
Here is a nice comparison though http://www.reddit.com/r/javascript/comments/1v4glc/react_vs_...
[+] [-] pkieltyka|11 years ago|reply
[+] [-] NicoJuicy|11 years ago|reply
The presentation is about the community (it's large) and about AngularJS 2.0.
AngularJS will become more usable with mobile dev.(with Material Design and famo.us). It will also expand to AngularDart
The poem is fun though when you like Angular: The poem https://twitter.com/NicoJuicy/status/525295632882614272
[+] [-] IkmoIkmo|11 years ago|reply
https://www.youtube.com/watch?v=cSCpGAPWe_8#t=166
Really looking forward to the integration of Material design in a mobile browser with Angular.