bakkdoor

It's completely down now.

On a german keyboard \ is not just "a single keystroke". What a pain -_-

"In the case of an acquisition of G-WAN's Copyrights, the new owner would be the best promotional player of parallelized architectures, and therefore a desirable partner for Intel, AMD, ARM, IBM and Oracle. This fact alone should sustain the disponibility of the product – whether TrustLeap or someone else maintains it"

.. right.

Gotta love their "insurance": http://gwan.ch/insurance o_O

this is insane.

I just added conditions & restarts today to Fancy (http://fancy-lang.org/). It's currently in a branch but it works =).

Yes.

The current implementation of futures uses a thread pool. I'm planning on changing this a bit to behave more like Io's actor model.

Hi, I'm the author of Fancy. The erlang-style actor message passing hasn't been implemented yet. I'm workin on that though. Rubinius has a built-in Channel type, (similar to go) and an Actor library built on top of it. Once I get some of the other language features I'm currently working on done, I'll focus on that part of the language. It just takes some time to get all these things finished, but it was always a goal to have this in the language. Rubinius also has inter-vm communication which I will expose in Fancy as part of the language as well. Another feature I'm currently working on is first-class pattern matching that preserves encapsulation (basically you have patterns as first-class values and matching an object against a pattern involves asking the object if it matches a given pattern - that way you don't break encapsulation). Hope that explains some of your concerns.

Yeah, I'll probably write up some of the stuff I've been doing with Fancy soon.

Btw, here's a list of current features I forgot to link to in the post: https://github.com/bakkdoor/fancy/blob/master/doc/features.m...

You mean symbol literals? Ruby uses :foo but that would mix up with the keyword message syntax. So I took Lisp's syntax: 'foo =) Also, since you'll want to have syntax for message names as well, they need to be able to have colons in them, e.g. 'foo:bar:. Basically anything non-whitespace starting with a "'" is taken as a symbol literal.

it's super effective!