On Wed, Feb 23, 2011 at 12:52:44PM +0300, Alexandre Prokoudine wrote: > On 2/23/11, Philipp Überbacher <[email protected]> wrote: > > > Example number one is the CUPS web interface, accessible using the > > obvious address http://localhost:631. First of all it gives me the > > creeps every time I have to use it, because I have to use the browser to > > modify my system. > > So problem number one is that you have old-fashioned view on system > configuration.
A realistic one I'd say. Using a web interface implies you have already a working system, and by no means a minimal one. > > Besides that the interface is slow and buggy, despite running on the > > same machine. I wouldn't call it a good interface in general. > > So problem number two is that because CUPS's UI is bad, you > extrapolate that on other web UIs. Very interesting. Apart from some very trivial ones I've never seen one that was any better. I've seen a lot of them that are a pain to use. > > The other example is google docs/spreadsheet which I have to use > > sometimes. There are the obvious privacy concerns, it should be clear > > that giving your possibly sensitive data to what's probably the worlds > > biggest Ad company isn't a good idea. > > So problem number three is conspiracy theories. Or elementary security awareness. If exposing the old and deprecated non-ssh based X11 interface is a bad idea (there's no discussion about that probably), then storing your data unprotected on a third party system certainly is. And then there are the legal issues. If you store some data obtained under NDA in a Google App, do you violate the NDA ? I'd say yes. What if a medical doctor stores his patient's files this way ? Most professional activities involve keeping confidential data of some sort. I would not hesitate to say that Google Apps is a no-go for that reason alone. Ciao, -- FA _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
