[tormeh]

My language's main feature was deterministic multithreading, of the synchronous school. It also forced a certain structure: All threads started and the shared variables they can write to have to be in the same area, arguments are always named, and sequence doesn't matter (optional in Python), shared variables can only be written to by one thread, but read by all. In contrast to some other deterministic multithreading solutions, the sequence in which IO is effected is also deterministic, not only the sequence of application to shared variables. The compiler had a typechecker and compiles to C++, using GCC to do the rest. I guess I should submit it to HN sometime...

[nickpsecurity]

That sounds interesting. Might be a decent stab at real-time programming and concurrency as it would need most of that.

"All threads started"

In many languages, the threads kind of sleep unless activated explicitly. Do you mean just the activated threads started or did you choose to have them all run at once for some reason?

"shared variables can only be written to by one thread, but read by all"

Good idea. BeOS also had read-many, write-one in form of benaphores: semaphores that only locked for writing. Strategy made it really fast.

"the sequence in which IO is effected is also deterministic"

What do you mean by that?

"compiles to C++"

The compile to C++ was my trick, too, since I knew I couldn't out-code GCC team. Although I wrote mine to avoid using C++ while being compatible lol...

"I guess I should submit it to HN sometime..."

You should. Either that or a forum where people discuss various language tradeoffs.