Sage Math Cloud
sagemath.blogspot.com
sagemath.blogspot.com
The basic issue for Sage is that it's gotten too large and complex, and too Linux-platform-dependent, to be a simple install on the majority of student machines. And with each new release, it's become larger and less accessible to many end users, most of whom run Windows on a limited-capacity PC.
Early on, someone created an installation package that ran Sage in a drop-in virtual machine that ran under Windows, but that approach quickly unraveled as Sage became larger and too much of a burden for a small system. This means that, at present, unless a person is willing to dual-boot Linux or run Linux alone, they can't run Sage locally.
Sage on a server has problems of its own -- which server, where, at what cost? But on the positive side, even when running on a single system, Sage behaves like a server-side application, so little needs to be changed for this strategy.
I hope this turns out to make Sage more popular and accessible -- IMHO it's a great mathematical tool, and the project's open-source philosophy only increases my respect.
My Sage tutorial: http://arachnoid.com/sage
Can you expand upon this? Not even Unix dependent, but precisely Linux? There's no hope of getting it to work with, say, homebrew on Mac OS X either?
Part of the issue for sage with tying into a lot of academic software is it has to tie into a lot of academic software, and that sort of stuff isn't always made with a lot of concern beyond 'can the graduate student compile it on the graduate student's machine and maybe the local cluster.'
I'm just surprised to see Sage getting accusations of grad-student level of maintainership code. Are they really scrambling that much outside of the mature math projects for code?
Any reasonably skilled server administrator can install Sage. But setting up user accounts and preventing server abuse are more important:
sage: N(pi,1e3)
3.14159265358979323846264338327950288419716939937510582097494459230781640628620899862803482534211706798214808651328230664709384460955058223172535940812848111745028410270193852110555964462294895493038196442881097566593344612847564823378678316527120190914564856692346034861045432664821339360726024914127
sage: N(pi,1e12)
(smoke starts pouring out of the server ...)
Wolfram Alpha solves this problem by timing out any transaction after a few seconds. I don't know how difficult that would be to set up in the Sage server.