sclytrack Wrote: > > How safe is "safe D" to run on your computer as if it is a client application. > > Let's say you want something like this. > > 1) The source is compared to the local one on the current disk. If the remote > version > is newer the new version is downloaded. > > 2) The source gets compiled and then executed in safe D but with only a subset > of phobos that can not alter anything permanent on the disk. (as if it is > a javascript client application). > > Like a replacement for HTML5 and javascript. > > ...or not suitable? > > I'm going to eat now.
SafeD is about memory corruption and not security. You'd have to provide your own system security through a framework and system administration.