Re:Classic computer science problems solved in JavaScript
by keefe on Saturday January 23, 2010 @12:46AM
(#1071417)
The more I work with js the more I like it. This project is a great idea, if it can be maintained. I'm fairly interested in figuring something to contribute myself.
Re:Classic computer science problems solved in JavaScript
by ComputerGuru on Saturday January 23, 2010 @10:28AM
(#1071912)
Look, JS is a language like any other. If I can do something in assembly, I can do it in JS. Give me IF statements (preferably with nesting support) and variables, and there's nothing that cannot be done.
What remains is how easy, how nice, how flexible, how enjoyable, how compatible, how reliable, how practical.
For me, the answer is C++, but don't let that influence you ;-)
Re:Classic computer science problems solved in JavaScript
by camccann on Saturday January 23, 2010 @12:26PM
(#1072085)
Give me IF statements (preferably with nesting support) and variables, and there's nothing that cannot be done.
I know you were exaggerating here, but simple conditional statements aren't actually sufficient. You need some construct that allows repetition, if only implicitly. "while" loops would be easy, but even simple function calls suffice if you have function pointers (in fact, allowing function pointers alone ought to be enough, without conditionals or even variables).
At any rate, it's the lack vs. presence of repetition constructs that makes SQL not a full general-purpose language, where XSLT actually is.
Re:Classic computer science problems solved in JavaScript
by pgbovine on Saturday January 23, 2010 @12:06AM
(#1071384)
i think the real value in doing js implementations is hooking them up to js visualization libraries so that you can do online demos within the webpage; could be great for education. otherwise i don't see the benefit of coding this up in js vs. other similar dynamic languages.
Re:Classic computer science problems solved in JavaScript
by walkon on Saturday January 23, 2010 @03:26AM
(#1071557)
Seriously asking here: what would you like more about Ruby as opposed to Javascript if they were in the same boat (i.e. if Ruby had client ubiquity, no systems frameworks, no major non-browser platform, etc)?
What remains is how easy, how nice, how flexible, how enjoyable, how compatible, how reliable, how practical.
For me, the answer is C++, but don't let that influence you ;-)
I know you were exaggerating here, but simple conditional statements aren't actually sufficient. You need some construct that allows repetition, if only implicitly. "while" loops would be easy, but even simple function calls suffice if you have function pointers (in fact, allowing function pointers alone ought to be enough, without conditionals or even variables).
At any rate, it's the lack vs. presence of repetition constructs that makes SQL not a full general-purpose language, where XSLT actually is.
At the assembly level, everything is boiled down to (basically) bne, mov, and jmp.
But popular? In what definition?
Just because it's used on almost every webpage, doesn't mean it's popular in the sense of being liked.