JavaScript For the Rest of Us 285
First time accepted submitter my2iu writes "The JavaScript programming language is both widely available and very powerful. Unfortunately, since only 6% of the world's population are native English speakers, the other 94% of the world are forced to learn English before they can start using JavaScript. Babylscript is an open source project that aims to translate JavaScript to all the world's languages, including French, Spanish, Chinese, and Arabic. The project has recently completed its 12th translation, enough so that the native languages of over 50% of the world's population are now supported!"
VBA? (Score:5, Insightful)
Because having local-language versions worked out so well for VBA - and that isn't even on the internet.
Re:VBA? (Score:5, Insightful)
Re:VBA? (Score:5, Interesting)
You should go visit Japan and Korea. EVERYTHING technical is done in local languages. Good english speakers are actually very hard to find even in top technical teams.
I suspect the same is the case in mainland china, although i have no first hand experience ( in Taiwan and Hong Kong english is everywhere )
Re:VBA? (Score:4, Insightful)
Re:VBA? (Score:5, Interesting)
Even here in Iceland where everyone is quite fluent in English (much moreso than in Japan), technical terms still are often handled in Icelandic. Aka, if you read the news about the Higgs announcement, it's not the "Higgs Boson", but "Higgs Bóseindin". It's not "centripetal force", but "miðflóttaafl". It's not "electromagnetic radiation", but "rafsegulbylgjir". Yeah, people sometimes use the English terms too (even for common words, some English words have become pretty much embedded in the language unfortunately), but in general, Iceland strives to avoid that. Even words for new products - computer is "tölva (number-prophet), phone is sími (old word for "line"), etc. The other Nordic languages don't do this sort of thing nearly as much.
Re:VBA? (Score:4, Insightful)
Hmmm... there's a simpler explanation for why French uses many similar words as English: I've heard it said that English is about 60% derived from French. It's really remarkable how many same/similar words between the two languages. The roots of English would explain why there's so many similarities. Instead of the French using English words, it's much more likely that it's the other way around. While on the other hand, Icelandic has probably close to 0% French origins.
Re: (Score:3)
While I agree with your point, your examples are hilarously irrelevant. Almost all of them are instances of English borrowing from French.
It's a consequence of roughly 80% of the English lexicon being of Romance origin, a large part of it through French (which brought also the words based on ancient Greek, lile politics and economy).
As a side note, in your last example, the Icelandic (TH)ú looks a lot like a cognate [wikipedia.org] to the deprecated English "thee", but IANALinguist.
Better examples of English loanwor
Re: (Score:3)
To be fair, my first example was "téléphone" :) And anyway, it gets hard with words that branched earlier to say who borrowed from who, as both languages have diverged from the branching point. But a couple of those words do not look like they follow traditional French naming conventions and instead look more like English naming conventions, suggesting a later borrowing.
Re: (Score:2)
I've seen programming languages using keywords in my native language (Dutch), and I found it silly, funny, and hard to be taken seriously. I just expect it to be English.
I also think way more than 6% of people, especially in software development circles, knows enough English to understand programming language keywords, compiler error messages, etc... And I'm sure there exist enough books in any spoken language about each programming language.
Re: (Score:3)
I haven't seen a Klingon manual for C++ yet
Re:VBA? (Score:4, Funny)
Actually, Knuth's "The Art of Computer Programming" reads much better in the original Klingon.
Re:VBA? (Score:5, Funny)
2 tonnes = 4409.24 pounds.
So, 2 tonnes is $6,927.02 at today's exchange rates?
Re: (Score:2)
Not if you're using Troy pounds it isn't
Re: (Score:2, Informative)
actually 1 tonne = 1000 kg
1 ton = 2000 lb
And this is different...??? (Score:5, Insightful)
Re:And this is different...??? (Score:5, Insightful)
I'm pretty sure that, aside from its dependence on Latin characters(which is, all in all, a good thing, Unicode would probably allow it to achieve malign sentience), TECO has no basis whatsoever in any human language.
GZ0J\UNQN"E 40UN ' BUH BUV HK /HKEX$$
QN
QQ/10UT QH+QT+48UW QW-58"E 48UW %V ' QV"N QV^T ' QWUV QQ-(QT*10)UH >
QV^T @^A/
Re: (Score:2)
0LT$$ (Score:2)
I love progamming in TECO. Because it feels so good when you stop!
Remember, EMACS was originally written in TECO. Does that tell you something about its author?
Re: (Score:3)
But learning TECO allows you to write a brainfuck interpreter and get into a state where writing in brainfuck feels like a blessing at the same time!
Re: (Score:2)
Not to mention that you'll have to learn English to use any library or are they going to translate all those as well.
As a non-native English speaker that has had the torture of seeing dutch and french VB/excel I can only hope that this never takes off.
Even localized EDI's are a silly idea.
If you want to learn to program learn English, you can do both at the same time and have access to so much more information.
Re: (Score:3)
Pascal was once a popular programming language. I've always felt one of the reasons C beat out Pascal is English, but maybe not. In Pascal a block is delimited with BEGIN and END, in C it's { and }. Pascal uses IF THEN and ELSE, C uses "if" and "else" but not "then", and these can be avoided with the ? : operator. C uses "for", Pascal uses FOR and TO (or DOWNTO). Pascal unnecessarily adds two more keywords with this REPEAT UNTIL structure, C gets by with one more keyword with "do while". In Pascal, ha
Re: (Score:2)
Quick question: What is more important?
1. Writing code
2. Being able to read code AFTER it has been written?
Sheesh... Most people in this world already face the problem you are talking about when they see everything written in English. And they are trying to fix it!
PS: Hopefully Slashdot fixes its commenting system. Months have passed since I posted anything and it is complaining that I have reused this form already!
Re: (Score:2)
Re: (Score:2)
Agreed completely. You don't need to go around translating internals. Just let me name my variables, function calls, etc properly, dang it! How hard can that be? Yet few programming languages seem to support that.
It's not even just about wanting to "write in a non-English language"; sometimes you're referring to actual proper nouns, and currently, the only solution is to mangle them. If I wanted to write a variable that holds data that gets sent to a system in (TH)orlákshöfn, I can't use any
Re: (Score:2)
And of course I can't even call it that here on Slashdot, because Slashdot mangles the thorn for some inexplicable reason, so I have to substitute letters. And this is just a comment website!
Slashdot's web server and webpages claim to support UTF-8, but the Slashdot backend treats it as ASCII and will helpfully display the ASCII 2+ character representation (sometimes these characters are unprintable).
For instance, here's a Euro currency symbol (U+20AC): â
However, HTML entities work. Here's a Euro currency symbol (€): €
As for thorn, I believe Þ and þ will give you the characters you want: and respectively... although I don't seem to see those, so maybe n
Re: (Score:2)
Yeah, that doesn't work either. :( It's just simply broken.
Re:And this is different...??? (Score:4, Interesting)
And doesn't writing javascript in, say, Arabic, just make it inaccessible to 99% of the people who like look at your code?
Yeah - it'll be interesting to find out what the LibreJS people think about it: https://www.gnu.org/software/librejs/ [gnu.org]
Re: (Score:2)
Yeah - it'll be interesting to find out what the LibreJS people think about it
Since LibreJS doesn't let you easily define your own version of Arabic, RMS will probably throw a hissy fit.
Re: (Score:2)
They should be able to have a program "translate" JS!Arabic to JS!English with relative ease. You just parse the script, replacing Arabic keywords with English keywords (that's even how I suspect they're doing it). You could probably even have an interpreter that can mix several languages.
I actually had a similar idea myself, years and years ago. Never did anything with it, though, and my plan was for C, not Javascript.
Oh, and in any case, comments and filenames often *are* in other languages already. So th
Re:And this is different...??? (Score:5, Interesting)
IIRC applescript had localized versions. There wasn't a problem in reading foreign scripts because keywords were translated (at one point keyword must be recognizable to the interpreter, that makes it relatively easy to translate them.
It is still not a good idea, of course. You need to copypaste a script from a blog and have it translated by the interpreter before understanding it.
And as a foreigner I can attest that the translation of keywords is a non-existent problem. Either you know the syntax of the whole command (parentheses, colons, semicolons, tabs, whatever) or you look it up. Once you have memorized it, could be english, your tongue, or LOLCODE, doesn't matter.
I'd possibly endorse localized versions of Logo and Smalltalk for basic teaching to kids. Everything else is overkill.
Re: (Score:2)
Once in a while I come across something that I know a little about, and then I wonder if everything I ever read and took as a wisdom was written but ignorant people on Slashdot.
Yeah I know... am I new here?
Have you ever been to China? Have you ever seen the code they run? Ever seen FORTRAN in Chinese characters? You think they should have learnt English first?
And you a foreigner! Really... I bet an Indian/European who already knew the Latin characters before he/she heard about JavaScript. There are billions
Re:And this is different...??? (Score:4, Insightful)
And as a foreigner I can attest that the translation of keywords is a non-existent problem.
As another foreigner, I can second that. I didn't know English when I started coding. I actually learned the basics by coding, and reading the docs. Similar ideas were floated then and some were actually implemented, and every time they were tried they were found to be an epic fail in practice, and most programmers (even those who didn't speak English beyond keywords in their favorite language) laughed at them.
Re: (Score:2)
How is this different than every other programming language I've ever encountered? And doesn't writing javascript in, say, Arabic, just make it inaccessible to 99% of the people who like look at your code?
That depends on whether it'll be 99% read by Arabs or not. There's several older code bases I've heard of here in Norway that's been written in Norwegian, simply because it was easier since it's our native language and you can use native terms the business side use in dealing with customers and they had no international ambition or plans to outsource. Well not the programming language, but the functions, the variables, the comments and so on. Changing the language itself would probably seem more natural, no
Re: (Score:2)
1. The keywords are localised, no other programming language I know have this capability.
2. Who cares? The point is not to give access of your source to others, it is to give easier access to the programming language itself to those who do not speak english.
I see this as an interesting idea. Why should I write "if" instead of "jos" (i.e. Finnish)? The latter is easier for Finns to understand and learn, especially if they are very young (or very old).
BTW, did you even read the article?
Re:And this is different...??? (Score:5, Insightful)
> I see this as an interesting idea. Why should I write "if" instead of "jos" (i.e. Finnish)? The latter is easier for Finns to understand and learn, especially if they are very young (or very old).
Except this idea was designed by people who have no clue how interpreters/compilers do their parsing.
So now I have to add *all possible potential translation words* as reserved for identifiers??
Using your Finnish example...
"English"; // OK, jos is not a reserved word IN English
var jos = 1;
if( jos ) console.log( "jos = " + jos );
"Finnish"; // FAIL, jos is reserved as 'if' in Finnish // ERROR: AMBIGUOUS
var jos = 1;
jos( jos ) console.log( "jos = " + jos );
Re: (Score:3)
Re: (Score:2)
functie test(i) {
als (i == 0)
retourneer waar;
}
Then your IDE could parse that and translate that to
function test(i) {
if (i == 0)
return true;
}
I'm not really in favor of this bec
sounds like a bad idea (Score:4, Interesting)
Considering current situation with XSS prevalence, javascript obfuscation techniques and content filters bypassing, this will only make matters worse
Forced to learn English to learn Javascript?! (Score:5, Insightful)
Re:Forced to learn English to learn Javascript?! (Score:5, Interesting)
Re:Forced to learn English to learn Javascript?! (Score:5, Funny)
Luckily, all human languages are isomorphic, so we can just draw up an unambiguous list of localized equivalents to each keyword, allow automated localization of javascript code without any possible ambiguity! What could possibly go wrong or undermine this glorious scheme?
(Other than comments, variable names, and the fact that languages are far from isomorphic?)
Re: (Score:2)
I can see the advantage in having the keywords be in your native language, for the most part the keyword itself gives some indication of its function and makes it much easier to remember and look up than it would a word in a different language.
Or you just provide documentation in the native language of the programmer that explains what the English keyword means rather than translating the keyword and doing nothing but cause confusion between programmers of different native languages?
No (Score:5, Insightful)
The programming language is the language, not the english language. You need to learn keywords, they could be klingon, do not need to make any sense for you. On the other hand, documentations are usually written in english.
Re:No (Score:4, Funny)
Nonsense. "(car (cddr (cadr (car x))))" is a perfectly understandable English sentence.
Re: (Score:3)
Re: (Score:2)
You need to learn keywords, they could be klingon, do not need to make any sense for you
Nonsense, all programmers know JavaScript as well as Klingon!
Oh non ... (Score:2, Funny)
C'est pas vrai!
Nonsense (Score:3, Informative)
Someone pulled this idea out of his ass and thought it was a genius idea.
Language keywords with accents? (Score:3)
I just took a look at the french translation:
charAt carÀ
charCodeAt codeCarÀ
indexOf indiceDe
lastIndexOf dernierIndiceDe
split fendre
substring souschaîne
I foresee thousands of text encoding bugs appearing everywhere this is used.
Re: (Score:3)
Such as wondrous Slashdot which still sucks at Unicode...
I'd be happy if I could just use variable names... (Score:2)
function calls, classes, etc which use letters that are not in the English character set. :P No translation needed, just let me type them without getting spammed with syntax errors like happens in most programming languages. And for that matter, I'd be happy if I could even *type* a thorn here on Slashdot without having it magically disappear.
Re: (Score:2)
I just typed two in this post - I certainly don't see them.
Yeah, let us all hide (Score:2)
Yeah, let us all hide in our ghettos again, very good for the world.
While very noble, all this native translation stuff and UTF-8, what I see is that more and more people stop trying to reach out and stay in their own culture/circle.
The internet 10 years ago was much more international oriented than it is nowadays.
Misguided (Score:5, Insightful)
I would hazard a guess and say that it's easier for a non-English speaker to learn normal JavaScript than it is for anybody to deal with this kind of nonsense.
I don't really see the advantage in this. You would be deliberately segregating yourself from the wider development community, and for what? Anglophones have to learn a lot of this stuff too. An asterisk doesn't mean multiplication to us, yet we learn that. Double ampersands don't mean "and", yet we learn that. Parentheses don't mean "do something", yet we learn that. The equals sign means "equals" in English, yet it's the assignment operator in JavaScript.
There are languages which are designed to more closely match natural language. AppleScript and Basic, for instance. There care also language which aren't very readable at all in English, such as LISP or Perl, that are still very successful. Natural language isn't really valued in the programming world for a variety of reasons. Sure, function calls might have some correspondence with English, but in the end, they are labels, not sentences, and everybody needs to learn what the labels mean precisely, even English people.
Re:Misguided (Score:4, Interesting)
Perl hard to read? I beg to differ!
http://www.perlmonks.org/?node_id=963133 [perlmonks.org]
Re: (Score:3)
I write my code in English so that everyone in the world can understand my source. Digging through a library written in French would be much worse than learning the meaning of a few words (that have little to do with their English meaning anyway).
Bad math, bad premise (Score:2)
Re: (Score:2)
I've always hated the argument that English is not the most widely spoken language because of "native" speakers. It is the most common second language that is learned throughout the world. And honestly, is the idea of having a single language that can be understood across the world so bad?
I'm all for translating documentation into a native language for more people to learn, but the programming language itself needs to be consistent across all uses. Otherwise, it's not the same programming language--just
Re: (Score:3)
English is also the language in which most of the computer-related neologisms originated. Leaving the terms in English makes them unambiguous whereas translating them has constantly been shown to do nothing but confuse people. This guy probably things he originated the idea of translating computer programming languages, but this has been done before many times and all such efforts have pretty much died out and for good reason: they suck.
Re: (Score:2)
English is also the language in which most of the computer-related neologisms originated. Leaving the terms in English makes them unambiguous whereas translating them has constantly been shown to do nothing but confuse people.
Yeah. I always argued that we in the rest of the world got the better bargain. The English had to dilute their language by giving new, high-visibility meanings to everything from Apache to zip.
Who came up with these awful translations? (Score:4, Insightful)
Re: (Score:2)
"char" is translated as "aeichen", which isn't even a word in German.
It's just a typo, the German word for "character" is "Zeichen", and the A and Z keys are next to each other (on a German keyboard as well as an international one). I wonder why it's not been capitalised though, nouns in German are supposed to be. If you're going to translate things, go all the way...
Re: (Score:3)
the A and Z keys are next to each other (on a German keyboard as well as an international one).
They're nowhere near one another on a German keyboard; the key below A is Y, and Z is next to T. Perhaps you were thinking of the French keyboard (AZERTY)?
Re: (Score:2)
This will not end well (Score:3)
Decades back I used a research OS that was developed pretty much along UNIX lines except that it was written in this Pascal variant where all the keywords were in French (Pascal was popular back then as a first language). It never achieved any traction & disappeared because neither the OS nor the language proposed anything really useful that you couldn't get already from Unix/C or just plain Pascal.
On a more recent level, one of the biggest PITA I and many others have with Office in non-english locales is that they translate the function names.
=sum(a1:a6) becomes =somme(a1:a6). I'ts easy enough to find websites that will help perform actions in Office, but I often spend twice the time finding out lust what wierd name MS has come up with for some VB function.
Is "pour" so much better than "for" for someone who is not a native english speaker? No, as by the time you have become proficient in the computer language, the subset of a foreign tongue it uses become well known & the difference irrelevant.
It looks to me that Babylscript is just a tool for the language bigots out there. Give it a few months & people will have forgotten it.
6% is just wrong! (Score:2)
You fail so completely.
http://en.wikipedia.org/wiki/List_of_countries_where_English_is_an_official_language#Sovereign_states [wikipedia.org]
I think that's more than 6%!
Re: (Score:2)
STOP! (Score:4, Insightful)
I hope this is a joke (Score:2)
Presumably these 94% will have put for foray into the javascript dom on hold until that gets translated.
The Japanese like to put their verbs at the end - are they going to accommodate that?
About half the planet like adjectives after the noun - so is going to be array new?
Re: (Score:2)
Are they also going to translate numbers?
In my native Dutch (nl-NL) locale, floating point numbers use a comma as decimal separator. So english "123.45" should be "123,45".
As I understand it, other locales also have differing floating point notation.
Really Necessary? (Score:2)
I learned programming in BASIC way before I learned English (my mother tongue is German). It didn't pose a problem at all, you have to learn the keywords character-by-character anyways, since you aren't allowed to make any stylistic modifications to the text. I don't quite see the point in this exercise, especially for languages that use the same writing system.
Additionally, programming nowadays is also about getting more information and help online. When you don't know English, most of the information onli
Way to make un maintainable code. (Score:2)
This is a really stupid idea!
Idiocy (Score:5, Insightful)
Will they also translate all the libs, the docs, the books out there?
IMHO This makes JS even less accessible and seriously increases the confusion factor.
the upside (Score:2)
Just think how many jobs this will add in the future, all those former COBOL coders retrained to fix Y2K, er, I mean, other-than-English version bugs...
Is it April 1 already? Surely they wouldn't really name it Babylscript, knowing what happened to the Tower's progress after language-splintering, would they?
Bloody good idea, chaps. (Score:2)
Finally use English programmers change the appearance of GUI widgets by their colour property!
This might be a bit imperialistic, but is a programmer who is not comfortable with English a good programmer? Since there is so much technical info in English, if your English skill aren't they good then you are going to miss out on a lot of good info. I seem to recall an interview with Linus Torvalds where he said that because all source code, etc, he ever saw was in English it never even occurred to him to code i
Re: (Score:2)
It's not imperialistic. English is the language of trade and science and is also the language from which the vast majority of computer-related neologisms originated. To have programming languages use English for its keywords makes it unambiguous to all users rather than you having some sub-par translated version that makes it impossible to use, say, MDN because you can't match up the keywords from the English version to your own.
More precisely (Score:2)
There are other important trade languages and, during the period when computers were getting started, German was still the language of chemistry and our R&D library had lots of engineering textbooks in German. If you don't know basic Italian and German you won't go far with opera. Musical notation is still Italian and I haven't noticed any moves to replace p and f in music
kind of silly (Score:2)
when a native English speaker learns a computer language, you might have to learn a function like, say for example, concat()
array1.concat(array2,array3,...,arrayX)
ok, I get it that concat is from the word concatenate. but concatenate, in English, can have all sorts of meanings, and in the context of javascript, that the meaning of the word concatenate should lend itself ONLY to the scenario of arrays, and ONLY to the meaning of joining arrays together... this is rather arbitrary
such that knowledge of Englis
/. united?? (Score:2)
Wow. I've read all the comments (that have been selected) and not one thinks this is a good idea.
Amazing to see everyone agree for a change.
"6% native English speakers" - is that relevent to anything? How many people can *read* (or write) English, as a 1st, 2nd, or nth language? - I'd guess somewhere over 75%, even higher if you consider the simple keywords used in javascript (not that knowing their meaning in real English will help enormously, as has been pointed out). Are there any complicated keywords? I
English! (Score:2)
It's the new Lingua Franca! No, wait...
Know english first to learn Javascript? (Score:2)
Javascript was better ... (Score:4, Funny)
in the original Klingon.
Step away from the computer please (Score:2)
Oh god, this is such a horrible idea. So they fixed the VBA problem where code developed for the German version of Excel fails to run anywhere else. Good for them. But then they claim that you can mix and match French and Spanish code. This is good how? As a German native speaker I was exposed a Java program written in German. For example, getters and setters were prefixed with "nimm" and "gib". My eyes start to bleed just thinking about it.
If you learn programming you have to deal with complex abstract pro
OffShore Programming (Score:2)
What a fucking great idea ! yeah !
Why don't you just write it in our beloved Universal Language "Esperanto" ? It should be even easier to maintain... It is UNIVERSAL !....
I believe that sometimes, if nobody invented a specific thing, maybe it's because this thing is fucking
Can software development deteriorate any further? (Score:2)
Once upon a time, when computers were not available to all, when it required an investment and expertise to write software, the higher barrier to entry essentially insured that, basically, only well qualified people were writing software.
Today, when anyone with 25 cents can write and compile software, it shows, I believe, in a lower overall quality of software and documentation. In those days I loved my software job; today the software overall sucks so bad I can't stand my job anymore.
This javascript 'enha
Really bad idea (Score:2)
This would be and incredibly stupid move. One of the greatest strengths of code is that it's a shared, common language. You can easily debug someone's syntax on usenet/blog/whatever without having to know their native language.
Sure it's nice to localize and cater to individual cultures, but the reason computer languages are so accessible to beginners is because they don't need to learn the language through google translate. Ever try and debug HelloWorld() in Arabic?
I had to learn English too! (Score:2)
I'm a "native" English speaker and guess what? I had to learn English too! I wasn't born that way!
Since 100% of JavaScript programmers have to learn at least some English, I demand they translate JavaScript into baby talk! It's not fair that my daughter will need to learn English before she can program.
What's the point? (Score:2)
One more translation needed... (Score:2)
Now, if we can only translate Javascript into a less painful scripting language, we'd have REAL progress! *insane laughter*
One more translation needed (Score:2)
Now, if they'd only translate Javascript into a less painful scripting language, we'd have REAL progress. *insane laughter*
Not the first language to have this done to it (Score:2)
This is not the first time somebody does this either, there is an entire industry in Russia built around a business platform (1 s) that prides itself by the fact that they have translated BASIC into Russian, I shit you not.
Bad Translation in German and some other issues (Score:3)
The German translation isn't good. They could've easyly improved on the syntax. let ist translated into 'sein' (to be) rather than 'lasse' (let). There are a few other instances were they could've actually improved on the language as a whole but messed it up.
Besides, as others have pointed out: The PL being in a different language than the native is an *advantage*. Less mixing of words. It's great to have native Variables and english keywords - it gives you way more flexiblity with your code.
My 2 cents.
Re: (Score:3)
Exactly. The German translation is horrible. It looks like one person just went over the keywords and translated them without considering the context they'd be used in. I'm pretty sure that nobody else checked on that translation before they decided to go with it.
The main problem seems to be that the translator decided to use the infinitive verb form for command/method names, when the imperative form would have been more appropriate.
E.g., arr.zerteilen(x) literally means arr.to_slice(x), not arr.slice(x
Overtranslating (Score:2)
Misleading stat (Score:2)
Unfortunately, since only 6% of the world's population are native English speakers
I've been to countries where the people do not speak English "natively" and I have been very surprised that most of the people speak English (as their second language) better than many people here in the US. While English may not be the first language of a significant portion of the world, English is spoken and understood by a very significant portion of the world's population.
Re: (Score:2)
Exactly. This is only good for making write-only code more prevalent.
Re:Really? (Score:4, Informative)
Re: (Score:2)
I'm *not* a native Icelandic speaker, but I still find it annoying that I can't program in Icelandic. No, not keywords like for, while, etc - translating those is an idiotic idea. I'm talking variable names, function names, class names, etc. Especially when I need to refer to proper nouns, it's annoying having to mangle my names for no good reason.
Re: (Score:3)
I'd go even further. When first learning to program, I was thrown more than once by thinking that a keyword meant something like its English definition would suggest. I would have learned quicker had the keywords been randomly selected from Dr. Seuss books.
Re: (Score:2)
Counter-Example of why this won't work: (From my previous post http://slashdot.org/comments.pl?sid=2990493&cid=40698389 [slashdot.org] )
"English"; // OK, jos is not a reserved word IN English
var jos = 1;
if( jos ) console.log( "jos = " + jos );
"Finnish"; // FAIL, jos is reserved as 'if' in Finnish // ERROR: AMBIGUOUS
var jos = 1;
jos( jos ) console.log( "jos = " + jos );
Now multiply ALL the keywords for EVERY language. This is a retarded idea.
So now the interpreter/compiler has to deal with this case? One possible solu