Mailinglist Archive: opensuse (4570 mails)
| < Previous | Next > |
Re: [SLE] Clearing up the FUD on CLI/Mono
- From: Randall R Schulz <rschulz@xxxxxxxxx>
- Date: Sun, 13 Nov 2005 00:35:03 +0000 (UTC)
- Message-id: <200511121634.59742.rschulz@xxxxxxxxx>
Anders,
On Saturday 12 November 2005 16:22, Anders Johansson wrote:
> On Sunday 13 November 2005 01:01, Steven T. Hatton wrote:
> > On Saturday 12 November 2005 03:00 pm, Steve Graegert wrote:
> > > What would be the rationale behind using C++ in .NET?
> >
> > C++/CLI is an ECMA standardization effort.
>
> Don't stare yourself blind at standards. The main issue is patents
>
> FWIW, I consider c++ to be one of the worst languages ever to not be
> designed. java in many ways is what C++ wanted to be, and with gcj's
> ability to compile to native code, it isn't that bad at performance
I'd think you'd not be given to folklore about program efficiency.
Static compilation to native code as gcj (or conventional C++) does it
is _not_ the best way to optimize performance. Java's so-called JIT
(it's really on-demand) native code compilation has optimization
opportunities not available when only static program analysis is
possible.
For all practial purposes and for a sizeable majority of programs, Java
is every bit as fast as C++ and what's more, the opportunities for
optimization of C++ are more played-out than are those for Java, which
is still improving its performance characteristics.
Randall Schulz
On Saturday 12 November 2005 16:22, Anders Johansson wrote:
> On Sunday 13 November 2005 01:01, Steven T. Hatton wrote:
> > On Saturday 12 November 2005 03:00 pm, Steve Graegert wrote:
> > > What would be the rationale behind using C++ in .NET?
> >
> > C++/CLI is an ECMA standardization effort.
>
> Don't stare yourself blind at standards. The main issue is patents
>
> FWIW, I consider c++ to be one of the worst languages ever to not be
> designed. java in many ways is what C++ wanted to be, and with gcj's
> ability to compile to native code, it isn't that bad at performance
I'd think you'd not be given to folklore about program efficiency.
Static compilation to native code as gcj (or conventional C++) does it
is _not_ the best way to optimize performance. Java's so-called JIT
(it's really on-demand) native code compilation has optimization
opportunities not available when only static program analysis is
possible.
For all practial purposes and for a sizeable majority of programs, Java
is every bit as fast as C++ and what's more, the opportunities for
optimization of C++ are more played-out than are those for Java, which
is still improving its performance characteristics.
Randall Schulz
| < Previous | Next > |