Hey, I'm back!

I'm one of the biggest fags here, but I see you managed to keep the faggotry at an sufficiently high level while I was banned (two weeks without 4chan... the horror, I actually did useful things), so good job!

Now, for something I discovered during my ban: Neko

http://nekovm.org/

Neko is a high-level dynamically typed programming language which can also be used as an embedded scripting language. It has been designed to provide a common runtime for several different languages. Neko is not only very easy to learn and use, but also has the flexibility of being able to extend the language with C libraries. You can even write generators from your own language to Neko and then use the Neko Runtime to compile, run, and access existing libraries.

I think this will become the new Reddit language (note, I do not read Reddit, so it might already have taken over) after Erlang dies out, just like Haskell did, and Ruby before that.

Weeaboo enterprise?

yeah so are you going to make somthing out of it or what?

Had a look at it and compared it to Python.

Things I like (bolded are things I like better than Python):
● Dynamic typing
● C-like syntax, = returns values
● First-class functions
● No statements (if, while, etc. are expressions)
● 1 / 0 = +infinity, this is great for trolling world4ch

Things I dislike (bolder are particularly grave failures compared to Python):
● Strings are sequences of 8-bit bytes (mega fail, worst thing in the language)
● Just "" to quote strings; I wanted Perl quotes or at least '' as well
● One word, the forced semicolon at the end of expressions
● if and while only treat "true" as true, WTF
● Automatic int/float <=> string conversion
● Shitty closures
● int, array, etc. are not objects (objects are not types) (Java anyone?)
● Doesn't specify mandatory tail call optimization

I prefer Python.

you can compile neko files that run in nekoVM with a language called haXe. http://haxe.org/. Good thing about haXe is that you can write flash swf files and javascript as well. check it out.

What sucks is to define new functions, you have to go:

var foo = function(x,y){...}
Wtf?

Also, I think their definition of 'Foreign Function Interface' is a bit iffy. You can't call exported from just any library, it has to be specifically written. See python ctypes for a real FFI mechanism.

It is not specifically designed to be written by a programmer, but rather to be generated from a higher level language.
then why the fuck do you want c-like syntax?

| One word, the forced semicolon at the end of expressions

LOL WUT

>>6
That's one of its best features, idiot. First-class functions, and no statements. If you don't like it, gb2/C with inline assembly.

>>8
Good point; if that were the true purpose then a LISP would have been the best choice.

>>10
I'll take your absense of comment on the FFI issue as a sign of agreement, thank you :P

>>11
Also its FFI sucks.

>>11
You know, if I disagree with you, I'll insult you; if I agree with you, I'll say nothing. That's how /prog works.

wat is program?

Lain.

Xarn is a bad boyfriend