Personally I don't; meaning it should be as good to run software in a jailed environment and not force the choice of language on developers.
I am curious to see what others think of this, though.
With a type safe language, being used alongside isolation mechanisms, I get two layers of protection, at language level and at the sandbox level.
Like Android or ChromeOS do with their managed environments + Linux SE and on Samsung's case Knox.
If the language is unsafe, everything outside the jail might be safe, but the program integrity or the data inside of the container are exposed to the attackers.
There are facilities and standards in most languages to help prevent this, but can you point out why this is not possible in Limbo? I'm not personally familiar with it.
Limbo does not support this, but both Java and .NET allow for security control at class and method level, however they tend to be misunderstood by most developers, which don't regularly use such features.
http://doc.cat-v.org/inferno/4th_edition/
It contains quite some useful information, including the book "Inferno Programming with Limbo" http://doc.cat-v.org/inferno/books/inferno_programming_with_...
Being a security oriented developer, I like that they decided to use a managed language for the whole userspace (Limbo) leaving C for the kernel and compatibility with UNIX software.
Basically, the distributed computing ideas and Oberon influences from Plan 9, merged with type safety.
In a certain way, what Android came to be, almost 20 years before it existed.