Would be interesting to hear if you discovered any downsides to Angular. I've been working with it a lot lately, but it seems to be a really good solution and the only issues with it is it can be hard to set up to be compatible with googlebot and the slightly tough learning curve
How to build a large Angular.js application
41–50 of 53 posts
Re: How to build a large Angular.js application
#42not as good as ng-boilerplate http://joshdmiller.github.io/ng-boilerplate/#/home with its modular cut and paste directory structure.
Re: How to build a large Angular.js application
#43Earlier quoted context omitted.
Rails is about 110,000 LOC, last I checked right before the 4.0.0 release, where'd you get that number?
$ git clone https://github.com/rails/rails.git && cd rails $ find . -name '*.rb' | xargs wc -l | tail -1 232424 total Maybe I should have said LOCC (lines of commented code)?
Re: How to build a large Angular.js application
#44> The core app is 9K lines of code. I don't think 9K is "large" for an application. At all.
For comparison, I work on a Backbone.js app that has the following distribution.
--------------------------------------------------------------------------------
Language files blank comment code
--------------------------------------------------------------------------------
Javascript 282 4348 7356 27860
CoffeeScript 336 4953 1687 17939
Obviously Backbone.js has much less "batteries" included.The tips in the article were good and well thought out. I appreciate the effort the author made.
Re: How to build a large Angular.js application
#45For example, http://Clara.io, our 3D design as a service offering, is already 52K LOC in just our core and that excludes the 30K LOC of external libraries.
Re: How to build a large Angular.js application
#46"Replacing Rails" seems silly. You can enable the asset pipeline in development if you really want. But most people would rather deal with slower page loads in development rather than debugging minified/uglified javascript in the console.
For dev / early testing I've just been using yeoman + grunt-connect-proxy with grunt spitting the final build files into the rails public directory to make it easy to push up to heroku. In final production you'd probably want to send your static assets to a cdn but that is easy enough.
Re: How to build a large Angular.js application
#47What are some large AngularJS projects that have been launched? I could only find Google DoubleClick and YouTube's PS3 interface. http://builtwith.angularjs.org/ Not to downplay the Ermahgerd Translator! http://ermahgerd.jmillerdesign.com/#!/translate
Re: How to build a large Angular.js application
#48> The core app is 9K lines of code. I don't think 9K is "large" for an application. At all.
9K LOC (not including comments) may not be "large" but it is quite sizeable and in a framework like Angular, probably does quite a bit. For comparison, I work on a Backbone.js app that has the following distribution. -------------------------------------------------------------------------------- Language files blank comment code -------------------------------------------------------------------------------- Javascr…
Re: How to build a large Angular.js application
#49What are some large AngularJS projects that have been launched? I could only find Google DoubleClick and YouTube's PS3 interface. http://builtwith.angularjs.org/ Not to downplay the Ermahgerd Translator! http://ermahgerd.jmillerdesign.com/#!/translate
I have a feeling AngularJS is the type of framework the will be used often for inside-the-firewall type of corporate apps than public facing consumer web stuff. But this is just my hunch right now and is influenced by my past building these style apps with Adobe Flex.
I'd be willing to bet that AngularJS will be hugely successful, and will gain a significant share of the Single-Page-App market.
Re: How to build a large Angular.js application
#50Earlier quoted context omitted.
I have a feeling AngularJS is the type of framework the will be used often for inside-the-firewall type of corporate apps than public facing consumer web stuff. But this is just my hunch right now and is influenced by my past building these style apps with Adobe Flex.
Have you built anything with AngularJS? I've built apps in both Flex and AngularJS, and to me AngularJS is a very different beast, and a much better beast. Unlike Flex, AngularJS: does not provide a UI component library, has a first-class runtime environment (that is growing, not shrinking), integrates into existing websites (rather than sitting inside them as black boxes), brings an MV* way of thinking with it (Flex…
I'm not saying Angular/Flex is the same beast. I'm saying that one of market segments that is going to find it most useful is the same people who were looking at Flex to solve problems back in 2006/07. Naturally, technology has progressed quite a bit since Flex came out. For a JS library, Angular hits a pretty good sweet spot for those same large dev teams looking to build native browser-based apps.