3 ms·
> We (the computing industry) did the single-address thing for many years. While using shitty languages, so not that relevant IMO. > But different languages a
by Ericson2314 11y ago
> We (the computing industry) did the single-address thing for many years.
While using shitty languages, so not that relevant IMO.
> But different languages are better suited to different tasks.
I think the industry can support multiple competing unikernels in different languages.
> ...tightly coupled...
Rigorously define ones interfaces while hiding implementation details :). Yeah it takes discipline, and OCaml/Rust/Haskell/etc are not able to codify all the invariants one might want to enforce. But as more powerful languages are polished, I believe that the situation will improve. I dream of a computing service where one submits software / with proof that it will "play nice" with other tenants, no hardware sand-boxing needed.
- dap 11y ago> I think the industry can support multiple competing unikernels in different languages. That way we can reimplement existing, common facilities not once, but N times -- and still not support what I was alluding to (namely, allowing specific subcomponents written in a language appropriate for that component). > Rigorously define ones interfaces while hiding implementation details Fine, but then there's little advantage to mandating a single address space and language.
- Ericson2314 11y ago> That way we can reimplement existing, common facilities not once, but N times -- and still not support what I was alluding to (namely, allowing specific subcomponents written in a language appropriate for that component). Ah sorry did not realize you meant that. Well the other answer is that more powerful languages can support more expressive and diverse embedded languages. > Fine, but then there's little advantage to mandating a single address space and language. Rigorous interfaces != primitive interfaces, but Unix forces both those on us. For example, how feasible is it to share a tree between to processes? Powerful languages allow us to specify the end-goals of per-process address spaces etc, while leaving the means much more open ended.