Live data from Hacker News

JavaScript is not suitable for large web apps

blogs.adobe.com

111–120 of 218 posts

Re: JavaScript is not suitable for large web apps

#111

"Help! I don't know how to organize code in intelligent ways! This is the fault of the language we originally decided to use!" I have to say after writing "large" web apps in PHP and also in 100% JS, I much prefer JS for front-facing stuff. I've not found organization to be a big issue...but maybe this is due to the fact that I use a JS framework for most of my larger apps (but then again, I did in PHP as well). Like…

> Also, you can't ignore that this is hosted by Adobe...

This may be true, but it's an ad hominem attack.

Re: JavaScript is not suitable for large web apps

#112

Earlier quoted context omitted.

>20 pricey smart JQuery guys See, this is how I knew you knew nothing about JavaScript. My bets, you're a manager that manages shitty Java coders who "used to code" and is an obnoxious know-it-all. Scale of 1-10, how close am I? Edit: From your website: "currentlly: BofA" (sic). Feeling pretty warm on my bet so far.

Like

Write intelligent comments that advance the discussion in some way. This is not reddit.

Re: JavaScript is not suitable for large web apps

#113
post #72

Unlike Steve Job's statement about ActionScript, Adobe's statement about JavaScript will not change the web landscape. Look at Google Docs for example!

I don't know the answer to this question, but it's worth posing: Is Google Docs written directly in JS? Or is it compiled down from, say, GWT?

Re: JavaScript is not suitable for large web apps

#114
post #84

Earlier quoted context omitted.

Not exactly - ActionScript3 is pretty much as close as you can get to what JavaScript2 would have been - Ecmascript 4.

...yeah, what was to be a beautiful language. So unfortunate that that proposal was squashed.

No, thank Thor that mutant was aborted. ECMAScript 4 got everything wrong, just like AS3 did.

Re: JavaScript is not suitable for large web apps

#115
post #87

Earlier quoted context omitted.

> First of all, put a comment at the top of your function that says what to expect about the return value. I want a language that gives me a nice pleasant syntax for doing that. And I want a magic pony; but as I said, declaring the return type doesn't tell users anywhere near all they need to know in many cases. Truly self documenting code doesn't exist, and will probably never exist. And since you can't usefully dis…

>And I want a magic pony; This magic pony exists. That's what the author is trying to say. You can write magic pony code, and it can be run as JavaScript. Magic Pony -> JS Conversion! Also, the OP doesn't have an issue dynamic languages as much as weak typed languages. It just happens that JS is weak and dynamic, while AS is strong and static. Having switched between Java, ActionScript and JavaScript for the last fou…

Just genuinely curious, as I assume it's some bit of Javascript weirdness I don't know, but why the tostring rigmarole over "obj instanceof Array"

Re: JavaScript is not suitable for large web apps

#116
post #72

Unlike Steve Job's statement about ActionScript, Adobe's statement about JavaScript will not change the web landscape. Look at Google Docs for example!

I don't know the answer to this question, but it's worth posing: Is Google Docs written directly in JS? Or is it compiled down from, say, GWT?

Google Docs are written using Google Closure JavaScript library, not Java/GWT

Re: JavaScript is not suitable for large web apps

#119
post #42

Is there any credible data on static vs. dynamic typing?

Yes. A couple of weeks back on either hacker news or reddit (I just searched, and could not find it quickly), there was a seemingly well conducted experiment, with a large number of students randomized to static and dynamic languages, that found no statistically significant difference.

Re: JavaScript is not suitable for large web apps

#120
post #25

Earlier quoted context omitted.

GWT? Seriously? I cannot think of any large, significant web app that has been written in GWT. I would consider the AWS management console to be significant.

It actually does a lot to explain why I hate the AWS management console so much.

Most people are users of the software, not developers, and so they hate the product because it's bad, not because it's written in Java.

Wait, you don't work for Amazon, so I'm confused...

Post reply on HN