Live data from Hacker News

JavaScript is not suitable for large web apps

blogs.adobe.com

51–60 of 218 posts

Re: JavaScript is not suitable for large web apps

#51
post #38

Earlier quoted context omitted.

Funnily enough, that also applies to: ActionScript, Dart, Java, PHP, node.js, Ruby, Go... ;)

node.js is written in JavaScript.

I am aware of that, but I personally use JavaScript to mean the browser language, and all the browser's features (DOM, WebSocket, etc.), but node.js to mean JS in the node.js environment. Same core language, but different environments, so not the same in practise.

Re: JavaScript is not suitable for large web apps

#53
post #46

Earlier quoted context omitted.

> 200 average developers This is the problem, and as you implicate, the exact sort of thing we need to stop doing.

Sure. So long as you have a full proof way of identifying the best developers. Hint: the best developers aren't the ones who can recite the API off hand.

You have to be willing to fire them if it turns out they're they suck.

Re: JavaScript is not suitable for large web apps

#55

This is more of a rant against dynamically typed languages than against javascript itself, and making the argument that dynamically typed languages are not suitable for large web apps is a difficult (not impossible) one to make. The author also complains about some javascript projects being split up into enough files, which is hardly a side-effect of using javascript. The author inherited what sounds like a pretty di…

And it's an Adobe blog. Their employees are quite likely to be biased in favour of their statically-typed variant, ActionScript 3 (well, it has a lot of changes, but it's essentially a JS variant at heart)

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

Re: JavaScript is not suitable for large web apps

#57
post #46

Earlier quoted context omitted.

> 200 average developers This is the problem, and as you implicate, the exact sort of thing we need to stop doing.

Sure. So long as you have a full proof way of identifying the best developers. Hint: the best developers aren't the ones who can recite the API off hand.

Fool. Fool proof. Not full.

Re: JavaScript is not suitable for large web apps

#58

Earlier quoted context omitted.

Sure. So long as you have a full proof way of identifying the best developers. Hint: the best developers aren't the ones who can recite the API off hand.

You have to be willing to fire them if it turns out they're they suck.

Average != suck.

Anyone who thinks they are going to do nothing but hire above-average programmers at any scale is downright naive. Design your system around an "average" employee, and you'll be far happier.

Re: JavaScript is not suitable for large web apps

#59

This is more of a rant against dynamically typed languages than against javascript itself, and making the argument that dynamically typed languages are not suitable for large web apps is a difficult (not impossible) one to make. The author also complains about some javascript projects being split up into enough files, which is hardly a side-effect of using javascript. The author inherited what sounds like a pretty di…

Glad you wrote it so I didn't have to. If you have programmers making bad decisions in any language a project quickly becomes unmaintainable. I say take it back.
Post reply on HN