Re: Octave 4.4 Proposal: make --no-gui the default

[sshah]

I support the proposal.

I see a number of problems with octave's gui model.   

First, it makes portability much harder -  gui version has not worked well
on Mac OS.   Homebrew version 4.2.2 builds without gui. 

Second, gui is not designed for remote use.  

For example, if you run octave-gui on Amazon AWS on any Linux instance, it
is basically not useable.   X-forwarding works with a little cajoling but
the user experience is poor.  This is because  even with network ping
latency of 30 ms, the user interaction in gui is painful. It does not help
that you have 30 + cores and 10 GB bandwidth for the instance.  

For the young users who grew up in the world of streaming video games, this
experience leaves much to be desired.  By contrast to octave-gui, Jupyter's
model of REST API on a browser remains far more useable under network
latency.  

This latency problem is true for remote VPN users connecting to
organization's private servers as well. 

  




--
Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html