On 6/14/13 2:23 PM, kcrisman wrote:
There are a number of tickets like #12232 (maybe six or seven) related
to the simple server API. This thread is to discuss the status of this.
Here are a few possible opinions.
1) This API hasn't worked for a long time well, and doesn't work at all
with the current notebook. So these tickets are unlikely to ever be
worked on in their current state and should be closed.
+1 for option (1)
wrt sage tickets vs sagenb tickets, I feel like sagenb might be reabsorbed
into sage at some point. People split it off as a separate project so they
could rapidly redo it in Flask, but development has really trailed off
since that big push in 2011, and Sage is switching to git anyway so sagenb
doesn't need to be a separate project to take advantage of DVCS
nimbleness. Plus now there's cloud.sagemath.org
<http://cloud.sagemath.org/> and the ipython notebook
so in the future sagenb might be fighting a war on two fronts (as a multi-
user UI and a single-user UI respectively) to stay relevant as a project.
Personally, I think what will eventually happen is that
cloud.sagemath.com will absorb the masses of crowds, and the IPython
notebook will develop to be good enough (with our input and help), and
sagenb as it currently exists will atrophy and be phased out. I don't
plan to work extensively on the sagenb codebase any time soon. My time
right now is taken up by the sage cell server and helping in what ways I
can with the IPython notebook/Sage integration.
Jason
--
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/groups/opt_out.
