OTP is written in erlang. The JVM is not "more low-level" and not "more general". In fact it is impossible to do on the JVM in any JVM language what the erlang VM gives you. You literally cannot replicate erlang on the JVM. You can fake it, but you will not have the guarantees and reliability that the erlang VM gives you.
To get erlang/OTP you would have to replicate it from the beginning in C, and there's no point in that, when you can just use erlang.
I think the point was more that Erlang was produced at considerable expense, so the cost of recreating Erlang for your own project is probably less than the cost of simply producing your project in Erlang.
I think the point was more that Erlang was produced at considerable expense, so the cost of recreating Erlang for your own project is probably more than the cost of simply producing your project in Erlang.
Fixed! Read your comment, understood it, but I think you probably meant the opposite
Comments
OTP is written in erlang. The JVM is not "more low-level" and not "more general". In fact it is impossible to do on the JVM in any JVM language what the erlang VM gives you. You literally cannot replicate erlang on the JVM. You can fake it, but you will not have the guarantees and reliability that the erlang VM gives you.
To get erlang/OTP you would have to replicate it from the beginning in C, and there's no point in that, when you can just use erlang.
That is a strange comment, ofc the Erlang VM is not the single best VM that will ever be created. Some day, someone will create a better one.
I think the point was more that Erlang was produced at considerable expense, so the cost of recreating Erlang for your own project is probably less than the cost of simply producing your project in Erlang.
Fixed! Read your comment, understood it, but I think you probably meant the opposite
I guess we'll just have to disagree on all of those points.