It's not practical to change the "skin" of JS this radically, but OTOH browser JS VMs are getting so fast that it *is* practical to compile CoffeeScript and other nearby source languages to JS. Heck, even Python -> JS in the browser is looking good, ignoring the standard library issue (http://skulpt.org/).
Your point, summarized as "Coding Style as a Failure of Language Design", was made recently by Robert O'Callahan. Perhaps you saw it? http://weblogs.mozillazine.org/roc/archives/2010/07/coding_style_as.html It is IMHO a good argument for language designers operating without backward compatibility and installed base constraints to consider. /be On Aug 27, 2010, at 3:15 AM, Irakli Gozalishvili wrote: > Hi, > > Please don't be too aggressive in replies, I know it's too ambitious & may > not lead to anything, but I still want to give it a try and suggest to: > > Employ some of the decisions that being made with coffee script & python in > order to over all the wars regarding: 2 space vs 4 space vs tabs, where to > put braces, whether or not use optional semicolons. All the style guidelines, > just hurt developers, who have to switch mentally every time they work on a > project with a different style guides. Besides if I follow correctly it's > being agreed to make backwards incompatible syntax changes in new version of > ECMAScript :) > > As a side note, I'd like to also mention that coffee script managed to reduce > verbosity so match, making writing code so much better experience! > > Regards! > -- > Irakli Gozalishvili > Web: http://www.jeditoolkit.com/ > Address: 29 Rue Saint-Georges, 75009 Paris, France > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
