By bloid
via theopensourcery.com
Published: Mar 04 2008 / 05:00
JavaScript ought to be forked - before the transition to JavaScript 2.0 makes a still relatively easy to use and approachable language inevitably OO cryptic, strong typing relentless, and large-scale programming oriented. JavaScript may fall into the Visual Basic and ActionScript traps. In the transition of those languages to undeniably very useful large-scale or complex distributed processing chores, both Microsoft’s Visual Basic and Adobe’s ActionScript for Flash, Flex and AIR have left a large constituency of small-scale scripting developers behind. These programmers now have the onerous burden of learning a lot of coding constraints which they simply do not need for most of their tasks; but have to have in order to work with their respective languages.
SaveShareSend
Tags: javascript, opinion
Comments
dzonelurker replied ago:
Easier said than done.
bscarr replied ago:
Voted down: Just because a feature is there doesn't mean you have to use it.
dzonelurker replied ago:
Voted up: Just because a feature is in the language does mean you have to know it (not use it).
domreiroam replied ago:
The proposition for ECMAScript 4 contains a lot of changes and some modify completely the philosohy of the language. I m not convinced that I would like all the changes. But I need to read again the proposition.
Voters For This Link (8)
Voters Against This Link (3)