public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: L A Walsh <cygwin@tlinx.org>
To: Paul Sheer <paulsheer@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Cygwin X11 Server slow performance
Date: Tue, 05 Jun 2018 16:00:00 -0000	[thread overview]
Message-ID: <5B16B381.7010205@tlinx.org> (raw)
In-Reply-To: <CABxOuY-XE-2-rB5hiOpJXOuxdZjVNaKkNveakq07dumfApu2Ww@mail.gmail.com>

Paul Sheer wrote:
>> 	Maybe you aren't familiar with 'X'.  X is just a graphical
>> transport.  It doesn't have menus unless some other program puts them up.
>> Try 'X' on linux -- running it from startX from a console and see
>> how easy it is to use.
>>
> 
> 
> NetSarang commercial X server has configuration menus to set keyboard
> mappings, cut-paste behavior, and various other settings in a user
> friendly manner.  It has orders of magnitude faster performance in a
> side-by-side comparison using XEmacs Motif as a test application
> displayed remotely over a 1GB LAN.
---
	That's fine, but how much does NetSarang cost for 10-15 years
of commercial support & upgrades?

	I use Gvim over a Gtk interface.  The fact that you are
comfortable with a 20 yr-old graphical interface, that was only
reasonably supported by commercial Unix vendors puts you in a
different class of users -- which was why I suggested an Apple
based OS in the first place.


> But that fact that you are using the reason "X is just a graphical
> transport" as an excuse makes me realize it is impossible to have a
> conversation with you.
---
	From my perspective, that's what it is, not too many 
programs are built on the Xlib et al. widget set.  I tune my programs
and I/O more for file I/O and know my toolsets enough to know that
they don't do with small packets, but had file I/O tuned at 
125megaB (mega=10**6) writes and 119megaB reads over a 1GB LAN
and now get 600+MB(M=2**20) reads and 275+ writes over a 8Gb LAN
(10 in name, but lose 20% to bus speed).  My speeds now, in file
I/O and in gvim are limited by CPU speed as Gvim does near full
syntax parsing for error and color display. 

	Realize though, that the fact that you prefer a commercial
emacs version to a free X11+gtk Gvim sorta puts you more in a
commercial apple class which is another reason I pointed at
Apple based computers.  Also, even the fact that you prefer emacs
+ motif...makes it less likely you'll be happy with something
that requires more work on the part of the user to tune for the
OS + hardware; again=> apple.

I hope you appreciate my input, it certainly wasn't from a fanboy
of any of the OS's, point of view, but you've indicated you want
Cadillac features and support.  I suggest and hope you find what
you are looking for.


(M=2**30) writes with 

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-06-05 16:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABxOuY8egyTzYbXGaTeyjt0AC=Wh5KQncmu3tj35KDk4k6hENw@mail.gmail.com>
2018-04-30  2:52 ` Paul Sheer
2018-04-30  2:59   ` Yaakov Selkowitz
2018-04-30  4:45     ` Brian Inglis
2018-04-30  4:48     ` Paul Sheer
2018-04-30 10:22       ` Marco Atzeri
2018-04-30 13:20       ` Andrey Repin
2018-06-05  0:24       ` L A Walsh
2018-06-05 14:50         ` Paul Sheer
2018-06-05 16:00           ` L A Walsh [this message]
2018-06-05 16:19             ` Paul Sheer
2018-06-05 20:24               ` Marco Atzeri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5B16B381.7010205@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin@cygwin.com \
    --cc=paulsheer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).