Erlang vs Java

Languages that run on a VM general.

Why do so many people hate Java and like Erlang?

Erlang is slooooooooow.

>>9
You have fuqin angered an [b][i][o]EXPERT PROGRAMMER[/o][/i][/b].

and no hardware isolation required, dipshit. FreeBSD Jails are run as an application, and each jail has its own process.

And how is process isolation achieved, dipshit?

If there's hardware bugs, nothing can be run in the machine, not even your stupid VM Design for just that language.

Suppose you have a machine that has the f00f bug. Any ``native code'' application you run can trigger it and freeze the entire machine. However, I fucking dare you to trigger it using an interpreted or VMed language (assuming the VM doesn't trigger the bug itself or generate native code that triggers it). My point is that on a secure system, only the superuser should be able to run non-VMed code (and the superuser [i]really[/i] shouldn't use that privilege unless absolutely necessary).

>>5 already mentioned languages suited for nearly all general tasks, including working in a VM, and implementing one, both safe and fault tolerant.

None of those languages are really ``dangerous'' from my point of view; to do ``pointer stuff'' in Scala or Scheme or CL you really need to go out of your way, and the languages are perfectly usable without ``escaping to hardware''. Can you say the same about C/C++ (I did that on purpose just because fuck you)?

This may be a communication problem, though. What exactly do you think my position is?