7 ms·

Didn't Google already write Google Apps and Google Maps in Java (or Go), and then compile it to Javascript? Because somebody at Google really doesn't like Javas

by bartl 14y ago

Didn't Google already write Google Apps and Google Maps in Java (or Go), and then compile it to Javascript? Because somebody at Google really doesn't like Javascript, and preferred to use something more "enterprisey".

kayoone 14y ago
GWT yes, which is some pretty impressive tech but limited to Java.
- andybak 14y ago
  Check out pyjs (née pyjamas): http://pyjs.org/ http://pyjs.org/
AndrewDucker 14y ago
Because, IIRC, trying to work on large systems with many developers doesn't work nearly as well without static typing.
- PommeDeTerre 14y ago
  When it comes to JavaScript, a team starts running into problems far sooner than they ever would when using C, C++, Java, C#, or more mature scripting languages like Python and even Perl. It's not at all difficult to create maintainable, reliable code bases in the aforementioned languages with hundreds of thousands, if not millions, of lines of code. Having a proper compiler or interpreter (and not just lint-style checkers) does help a great deal. Having a sensible language to begin with also helps. When using JavaScript, the problems start arising much, much sooner. It just doesn't offer the language features necessary for anything much beyond short scripts. An undisciplined team using JavaScript will run into problems when approaching a mere thousand lines of code. Their software will be unmaintainable if it ever manages to get into the tens of thousands of lines. Even teams of the best, most experienced and most disciplined JavaScript developers often start running into problems once into the tens of thsouands of lines of code. After having witnessed this on many projects, it becomes clear that using some other language is the best option, even if it's converted to or compiled down to JavaScript in the end.
- daigoba66 14y ago
  Large systems, in my opinion, generally benefit from static typing.
dougk16 14y ago
A little old, but here are some internal use cases for GWT at Google: https://groups.google.com/forum/m/?fromgroups#!topic/google-web-toolkit/Mjjk5y9RQbw https://groups.google.com/forum/m/?fromgroups#!topic/google-... I don't think it comes down to not liking JS. JS has its uses, but you get quickly diminishing productivity returns as your application gets larger and hairier. I've actually had a project where the "M" and the "C" (of MVC) was written in GWT-able Java, and the view with JS. Right tool for each job.

by bartl 14y ago

kayoone 14y ago

GWT yes, which is some pretty impressive tech but limited to Java.

andybak 14y ago
Check out pyjs (née pyjamas): http://pyjs.org/ http://pyjs.org/

AndrewDucker 14y ago

Because, IIRC, trying to work on large systems with many developers doesn't work nearly as well without static typing.

PommeDeTerre 14y ago
When it comes to JavaScript, a team starts running into problems far sooner than they ever would when using C, C++, Java, C#, or more mature scripting languages like Python and even Perl. It's not at all difficult to create maintainable, reliable code bases in the aforementioned languages with hundreds of thousands, if not millions, of lines of code. Having a proper compiler or interpreter (and not just lint-style checkers) does help a great deal. Having a sensible language to begin with also helps. When using JavaScript, the problems start arising much, much sooner. It just doesn't offer the language features necessary for anything much beyond short scripts. An undisciplined team using JavaScript will run into problems when approaching a mere thousand lines of code. Their software will be unmaintainable if it ever manages to get into the tens of thousands of lines. Even teams of the best, most experienced and most disciplined JavaScript developers often start running into problems once into the tens of thsouands of lines of code. After having witnessed this on many projects, it becomes clear that using some other language is the best option, even if it's converted to or compiled down to JavaScript in the end.
daigoba66 14y ago
Large systems, in my opinion, generally benefit from static typing.

dougk16 14y ago

A little old, but here are some internal use cases for GWT at Google: https://groups.google.com/forum/m/?fromgroups#!topic/google-web-toolkit/Mjjk5y9RQbw https://groups.google.com/forum/m/?fromgroups#!topic/google-... I don't think it comes down to not liking JS. JS has its uses, but you get quickly diminishing productivity returns as your application gets larger and hairier. I've actually had a project where the "M" and the "C" (of MVC) was written in GWT-able Java, and the view with JS. Right tool for each job.