Earlier quoted context omitted.
I thought Gmail was a compiled to JavaScript from Java application?
Nope, you're thinking of GWT. Relatively few Google products actually use GWT; the bulk of them are on Closure. GMail's client (and Google+, and Docs, and Search) all use Javascript-compiled-to-Javascript for the client side.
Things that suck in AngularJS
81–90 of 151 posts
Re: Things that suck in AngularJS
#82I found Angular to be overly complex and couldn't imagine training a team to learn to use it in reasonable time. That's the scariest part of adopting Angular for me. How would other coworkers adapt to the API and how long would it take for them to use it? The documentation was o.k at best, but I find that isn't the core issue. If you take a look at http://docs.angularjs.org/guide/concepts , it takes a very long time…
Re: Things that suck in AngularJS
#83While that used to be true, the directives page recently got updated to provide a much better and simple guide to directives along with plently of code samples - http://docs.angularjs.org/guide/directive
Re: Things that suck in AngularJS
#84Earlier quoted context omitted.
Nope, you're thinking of GWT. Relatively few Google products actually use GWT; the bulk of them are on Closure. GMail's client (and Google+, and Docs, and Search) all use Javascript-compiled-to-Javascript for the client side.
I've always wondered why GWT isn't much more popular (at least, for google properties). I know of a half dozen apps written in GWT by google. The rest is probably in closure (or something else). Perhaps they still haven't solved the SEO problem of GWT internally, and so only things that don't need SEO-features like control panels, dashboards (but ironically, the google groups forums too) are in GWT.
I don't think the SEO nature of GWT is fundamentally different from Closure or Angular.
Re: Things that suck in AngularJS
#85Ron Swanson approves this message.
Re: Things that suck in AngularJS
#86Earlier quoted context omitted.
With this many people saying the documentation could be improved, is there a reason holding everyone back from contributing or improving it?
The barrier of having to contribute via GitHub is actually a fairly large one. Think about it; not even all developers understand git. The design challenge of creating a simple way to contribute/improve documentation (read: educational materials ) is something we're working at Coursefork [1]. It's a tough one to solve, but we think we've cracked it. [1]: http://coursefork.org
Re: Things that suck in AngularJS
#87Earlier quoted context omitted.
It's not so common because: - It requires a running JVM to compile it all down (not a bad thing). - Can take upwards of a second to compile depending on code base size and compression setting (even if the JVM is warm). - Kills all ability to debug. Looks like "a.call().call()" etc. That said, ClojureScript has been fun to work with, but IMO, Google Closure as dependency thwarts a lot of people looking to try it out l…
i m certain you can pretty print the resulting compiled js. see http://googleclosure.blogspot.com.au/2010/10/pretty-print-ja...
Re: Things that suck in AngularJS
#88Earlier quoted context omitted.
Maybe my understanding is wrong, but closure (and closurescript) are compiled languages. Angular is a UI framework, so comparing them is apples to oranges. And I think the Angular community would be thrilled if it had even close to the kind of documentation that Rails has. You are correct, no one framework will rule them all, but there are examples of OS projects that have good docs (like jQuery and Rails) that can b…
You may be thinking of Clojure and ClojureScript — with a J. It's confusing naming, but those are different, and are not Google products. In this thread, we're talking about Google's Closure (with an S) Library. Google also makes a Closure (with an S) Compiler, but it's more of an optimizer — it "compiles" from JavaScript to optimized JavaScript.
Re: Things that suck in AngularJS
#89Re: Things that suck in AngularJS
#90Earlier quoted context omitted.
I've always wondered why GWT isn't much more popular (at least, for google properties). I know of a half dozen apps written in GWT by google. The rest is probably in closure (or something else). Perhaps they still haven't solved the SEO problem of GWT internally, and so only things that don't need SEO-features like control panels, dashboards (but ironically, the google groups forums too) are in GWT.
GWT is seen as extremely slow (especially compilation times) and not suited to heavy client-side applications. I don't think the SEO nature of GWT is fundamentally different from Closure or Angular.
http://www.google.com/fonts (ps, i have no affiliation with google, i just don't like mistunderstood tech to suffer…)