2009/2/25 Michael Rueger <[email protected]>: > Igor Stasenko wrote: > >>> The core issue about having FFI or Alien available in the standard >>> system is that then people start coding against it. One you go down that >>> road, it is hard to reverse that and make a system "sandboxable". >>> >> >> sound like: >> a) isolationists tactics >> b) teaching others how to write good code >> >> i really don't like when people deciding upfront what is good or bad >> and don't providing any choice how to change this. >> This is against the spirit of smalltalk. >> Use java then, with its sealed classes :) > > I think you are missing the point. > An example: > in order to get the MIME type of a file on a Mac you can use a certain > system call to do that. There two choices: you write or extend a plugin > (sandbox safe, but a lot of work) or you use FFI/Alien (not sandbox > safe, but quick to do and maintain). > I think you miss the point. :) If VM in control whether allow or disallow FFI calls then you get much more security than leaving it to be handled by OS and hoping that there is no squeakFFI library in same directory where VM located or in one of the search dirs.
> If FFI is not default, then people tend to do the extra work to work > with a plugin. > If it is available, people will avoid that extra work and I think that > is absolutely legitimate and has nothing to do with good or bad code. > can't take it as a strong argument. Maybe Croquet doing it in wrong way by using FFI to make GL calls. But it was ultimately their own choice. To encourage people to write a plugins instead of use of FFI, a better way would be to improve VMMaker tool and simplify VM building procedure. But limiting people from use of FFI in hope that they eventually start writing plugins i think is spoiled idea. > Michael > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
