5 ms·
OK that was a bad example. I just meant to say that C compatibility is an over-specification. We just need machine level interfacing like maybe locking to hardw
by karmakaze 8y ago
OK that was a bad example. I just meant to say that C compatibility is an over-specification. We just need machine level interfacing like maybe locking to hardware threads, fixed address referencing, etc.
Edit: I don't know much about this but it might be a better example "GRiSP 2 – Erlang and Elixir on bare metal." I'm assuming this is possible and includes the BEAM VM with GC.
https://news.ycombinator.com/item?id=19358133 https://news.ycombinator.com/item?id=19358133
- brightball 8y agoThe BEAM GC is a little bit special because there’s not a shared memory model. Millions of little Erlang processes will be GC’d independently which simplifies things a ton. That isolation model probably wouldn’t translate to the greater code ecosystem even though it’s very effective for BEAM applications.
- ldng 8y agoOh I see, you mean "unvirtualizing" the VM and run on the hardware that comply to the VM spec. I was under the impression that generally VM are idealized hardware that is friendlier for software development but they would make terrible actual hardware. I suppose it also depend on the language/VM. But I'm totally out of my comfort zone. Let wait and see if someone more knowledgeable chimes in :-)