Link Details

Link 100935 thumbnail
User 111696 avatar

By bloid
via dobbscodetalk.com
Published: Aug 05 2008 / 06:52

I expect a new language iteration to correct major flaws, reduce ambiguity in the specification, and make small tweaks to the language. ECMAScript 4 does this, but it also adds a type-system, new binding primitives, and a dozen other new features! What seems to have happened, is that the designers are attempting to turn ECMAScript into a language that is appropriate for larger scale programming.
  • 8
  • 2
  • 805
  • 188

Comments

Add your comment
User 212444 avatar

bscarr replied ago:

1 votes Vote down Vote up Reply

Voted down 'cos the author is moaning over nothing. The changes to ES4 are backwards compatible with ES3, therefore, you are not compelled to use them. If you want to script use the features pertinant to scripting and leave the other features alone.

User 311881 avatar

stugots replied ago:

0 votes Vote down Vote up Reply

@Barry: The author's concern is right on. Once a language gets a new feature, it's there forever. Deprecating a feature is a huge energy drain on the desigers, documenters, implementers, and users. Another point is that simplicity is powerful, and these changes appear to be anything but.

User 283139 avatar

ceaseoleo replied ago:

0 votes Vote down Vote up Reply

i like where they are heading with ecma script. By adding structure, and features that are useful from other languages, they are increasing the user base, and code quality. For example these changes should promote better coding practices ( in theory) .

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (8)



Voters Against This Link (2)