3 ms·

"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 "lar

"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 C "feels" like a language for low-level programming and PHP "feels" like it should be running on a webserver, javascript "feels" like it's right at home in the browser. And now that browsers are powerful enough to be the entire front-end, I've come to completely embrace JS for this task. Javascript is not a bad language. It's a very powerful language. Just like any other language, if it's poorly organized it's going to be a mess. I can tell you, from my experience, it is suitable for large web apps!! Also, you can't ignore that this is hosted by Adobe...

Zimahl 14y ago
"Help! I don't know how to organize code in intelligent ways! This is the fault of the language we originally decided to use!" The problem might not be you. Once you are done with your organized code and are moved to another project, some 'junior' dev gets a hold of your stuff and makes simple mistakes that static-typed languages could've avoided. I'm not anti-JS btw, just throwing out one possibility.
- unconed 14y ago
  Big surprise: junior developers who've only been taught to architect for statically typed language are lost in dynamic languages.
munificent 14y ago
> Also, you can't ignore that this is hosted by Adobe... This may be true, but it's an ad hominem attack.
- lowboy 14y ago
  It might be ad hominem out of context, but I don't feel it's improper to question the motives of someone working for a company that would most likely benefit from a decline in javascript in the app space. http://en.wikipedia.org/wiki/Ad_hominem#Questions_about_the_notion_of_an_ad_hominem_fallacy http://en.wikipedia.org/wiki/Ad_hominem#Questions_about_the_...
  - hatsix 14y ago
    How would Adobe beneifit from a decline of javascript?

Zimahl 14y ago

"Help! I don't know how to organize code in intelligent ways! This is the fault of the language we originally decided to use!" The problem might not be you. Once you are done with your organized code and are moved to another project, some 'junior' dev gets a hold of your stuff and makes simple mistakes that static-typed languages could've avoided. I'm not anti-JS btw, just throwing out one possibility.

unconed 14y ago
Big surprise: junior developers who've only been taught to architect for statically typed language are lost in dynamic languages.

munificent 14y ago

> Also, you can't ignore that this is hosted by Adobe... This may be true, but it's an ad hominem attack.

lowboy 14y ago
It might be ad hominem out of context, but I don't feel it's improper to question the motives of someone working for a company that would most likely benefit from a decline in javascript in the app space. http://en.wikipedia.org/wiki/Ad_hominem#Questions_about_the_notion_of_an_ad_hominem_fallacy http://en.wikipedia.org/wiki/Ad_hominem#Questions_about_the_...
- hatsix 14y ago
  How would Adobe beneifit from a decline of javascript?