On Fri, Aug 22, 2014 at 4:42 AM, Volker Braun <vbraun.n...@gmail.com> wrote:
> That is not so unlike the current VM which runs the sage notebook web > server. You can then connect to it with the host browser, if you want (it > does pop up a browser inside the VM because 1. why not and 2. firewall > issues). Yup, I know that's how it currently works. But with this proposal: - a headless VM is less 'alien' to user. T\(they can use their familiar browser, extensions, etc, and they don't have to see a new desktop. The whole 'destkop in a desktop' can be confusing to new users. - it's also far lighter in resources. Much smaller disk image, memory footprint and runtime overhead, since you only deploy a tiny container instead of a full-blown desktop envrionment. - users see their normal filesystem and tools, and they can install and manage the non-sage parts of the runtime with tools that work well on Windows like Anaconda or Enthought Canopy (or even do a manual install if they so desire, the dependencies are all easily pip-able). As I said, just an idea for you guys to consider, since I know that a good Windows experience is still an elusive goal. Cheers, f -- Fernando Perez (@fperez_org; http://fperez.org) fperez.net-at-gmail: mailing lists only (I ignore this when swamped!) fernando.perez-at-berkeley: contact me here for any direct mail -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
