From: Brent Cook <bcook@bpointsys.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: piet@bluelane.com, netdev@vger.kernel.org,
Stephen Hemminger <shemminger@osdl.org>,
David Miller <davem@davemloft.net>, Andi Kleen <ak@suse.de>,
piet at work <piet@work.piet.net>,
Rajneesh Saini <rksaini@gmail.com>
Subject: Re: Alternate to Ixia's ANVL test harness for tcp compliance.
Date: Thu, 20 Jul 2006 16:47:14 -0500 [thread overview]
Message-ID: <200607201647.15334.bcook@bpointsys.com> (raw)
In-Reply-To: <44BFF644.2020507@garzik.org>
On Thursday 20 July 2006 16:31, Jeff Garzik wrote:
> Piet Delaney wrote:
> > I wonder if Microsoft is providing the "big challenge" to porting the
> > same GUI to linux. The world really doesn't need yet another Java
> > language. Gosling is a Genius, I studied his X11 News Server enough
> > to know first hand. Microsoft lost in court with their violating the
> > Java standards and C sharp seems to be just another stratagy to their
> > bizarre attempt to world domination (Like the SCO mess).
>
> Runtime dynamic bytecode languages -- Java, Perl, Python, Ruby, ... --
> do seem to be all the rage.
>
> As DaveM noted, though, C# is fully supported under Linux.
>
> Or maybe they could go for Gtk+, which has successfully been used to
> maintain complex GUIs apps on both Windows and Linux. GIMP is the most
> notable example, but use of Gtk+, GLib, and mingw has meant that you can
> build Linux-ish apps on Windows without nasty porting layers like Cygwin.
>
> Jeff
>
Base C# support is pretty good in Mono, but you still have to be quite careful
when creating a cross-platform application with it. Microsoft's version
implements a number of libraries that still are not quite as well implemented
in Mono (if at all). The toolkit libraries (Windows Forms, to the latest
stuff with Vista) are a bit of a moving target. Plus, the .Net platform still
lets developers interact with COM objects and other Windows-only code.
Just because the GUI is C# does not mean that it does not have a number of
Windows-only dependencies, unless it was implemented with portability
in-mind.
next prev parent reply other threads:[~2006-07-20 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 19:49 Alternate to Ixia's ANVL test harness for tcp compliance Piet Delaney
2006-07-20 20:04 ` Jeff Garzik
2006-07-20 20:24 ` Piet Delaney
2006-07-20 21:17 ` David Miller
2006-07-20 21:31 ` Jeff Garzik
2006-07-20 21:42 ` Piet Delaney
2006-07-20 21:47 ` Brent Cook [this message]
2006-07-20 21:56 ` Jeff Garzik
2006-07-20 20:08 ` jamal
2006-07-20 20:28 ` Andi Kleen
2006-07-20 20:43 ` Tomasz Torcz
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=200607201647.15334.bcook@bpointsys.com \
--to=bcook@bpointsys.com \
--cc=ak@suse.de \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=piet@bluelane.com \
--cc=piet@work.piet.net \
--cc=rksaini@gmail.com \
--cc=shemminger@osdl.org \
/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 NNTP newsgroup(s).