From: Pal-Kristian Engstad <pal_engstad@naughtydog.com>
To: Yoann Padioleau <padator@wanadoo.fr>,
"caml-list@yquem.inria.fr" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] stl?
Date: Wed, 04 Mar 2009 13:51:40 -0800 [thread overview]
Message-ID: <49AEF7EC.2000809@naughtydog.com> (raw)
In-Reply-To: <8763ipypx1.fsf@aryx.cs.uiuc.edu>
[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]
Yoann Padioleau wrote:
> Jon Harrop <jon@ffconsultancy.com> writes:
>
>> I'm very happy to see C++ dying.
>>
>
> Is it ?
>
C++ is definitely not dying.
Here are some reasons:
* Most high-level languages decide the format of your data for you.
This is good for most things, but if a large part of your
application needs specific data layouts, then you are out of luck.
* Most high-level languages can not support multiple forms of data
allocations. Some applications need a range of allocation
strategies, ranging from completely automatic (garbage collection)
to completely manual.
* Most high-level environments do not allow for fine-grained control
of computing resources, e.g. soft real-time guarantees.
* Most high-level languages do not allow for C/C++ intrinsics, for
instance leveraging access to the SSE registers.
* Most high-level languages do not allow for fine-grained control,
for instance allowing different forms of threading mechanisms.
Of course, you can always say that you can use the foreign function
interface, but then you lose inlining and speed. More importantly, you
end up with a project with several different languages. That is
generally a very bad idea.
In short, most high-level languages will remain used for only for toys
and applications where speed and resource constraints is of no concern.
Which is sad, because C++ has many, many problems - the most major one
being that it is so easy to produce bugs.
Thanks,
PKE.
--
Pål-Kristian Engstad (engstad@naughtydog.com),
Lead Graphics & Engine Programmer,
Naughty Dog, Inc., 1601 Cloverfield Blvd, 6000 North,
Santa Monica, CA 90404, USA. Ph.: (310) 633-9112.
"Emacs would be a far better OS if it was shipped with
a halfway-decent text editor." -- Slashdot, Dec 13. 2005.
[-- Attachment #2: Type: text/html, Size: 2487 bytes --]
next prev parent reply other threads:[~2009-03-04 21:53 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 21:40 stl? Raoul Duke
2009-03-03 22:31 ` [Caml-list] stl? Yoann Padioleau
2009-03-03 22:42 ` Till Varoquaux
2009-03-03 23:36 ` Jon Harrop
2009-03-04 0:13 ` Peng Zang
2009-03-04 0:58 ` Yoann Padioleau
2009-03-04 1:10 ` Raoul Duke
2009-03-04 1:19 ` Pal-Kristian Engstad
2009-03-04 1:21 ` Yoann Padioleau
2009-03-04 1:29 ` Jon Harrop
2009-03-04 14:26 ` Kuba Ober
2009-03-04 14:24 ` Kuba Ober
2009-03-03 23:42 ` Jon Harrop
2009-03-04 0:11 ` Brian Hurt
2009-03-04 1:05 ` Yoann Padioleau
2009-03-04 4:56 ` Brian Hurt
2009-03-04 20:11 ` Yoann Padioleau
2009-03-04 21:59 ` Brian Hurt
2009-03-04 22:42 ` Yoann Padioleau
2009-03-04 23:19 ` Jon Harrop
2009-03-04 23:03 ` Jon Harrop
2009-03-11 3:16 ` Brian Hurt
2009-03-11 5:57 ` David Rajchenbach-Teller
2009-03-11 6:11 ` David Rajchenbach-Teller
2009-03-04 1:59 ` Jon Harrop
2009-03-04 6:11 ` Brian Hurt
2009-03-04 14:08 ` Christophe TROESTLER
2009-03-04 14:19 ` Peng Zang
2009-03-04 16:14 ` Brian Hurt
2009-03-04 16:35 ` Andreas Rossberg
2009-03-04 16:40 ` Peng Zang
2009-03-04 21:43 ` Nicolas Pouillard
2009-03-05 11:24 ` Wolfgang Lux
2009-03-04 19:45 ` Jon Harrop
2009-03-04 21:23 ` Brian Hurt
2009-03-04 23:17 ` Jon Harrop
2009-03-05 2:26 ` stl? Stefan Monnier
2009-03-04 3:10 ` [Caml-list] stl? Martin Jambon
2009-03-04 6:18 ` Brian Hurt
2009-03-04 16:35 ` Mikkel Fahnøe Jørgensen
2009-03-04 16:48 ` Yoann Padioleau
2009-03-04 20:07 ` Jon Harrop
2009-03-04 20:31 ` Richard Jones
2009-03-04 20:49 ` Yoann Padioleau
2009-03-04 21:20 ` Andreas Rossberg
2009-03-04 21:51 ` Pal-Kristian Engstad [this message]
2009-03-04 22:50 ` Jon Harrop
2009-03-04 23:18 ` Pal-Kristian Engstad
2009-03-05 1:31 ` Jon Harrop
2009-03-05 2:15 ` Pal-Kristian Engstad
2009-03-05 3:26 ` Jon Harrop
2009-03-05 6:22 ` yoann padioleau
2009-03-05 7:02 ` Raoul Duke
2009-03-05 8:07 ` Erick Tryzelaar
2009-03-05 9:06 ` Richard Jones
2009-03-05 9:34 ` malc
2009-03-05 9:56 ` Richard Jones
2009-03-05 10:49 ` malc
2009-03-05 11:16 ` Richard Jones
2009-03-05 12:39 ` malc
2009-03-05 19:39 ` Jon Harrop
2009-03-05 21:10 ` Pal-Kristian Engstad
2009-03-05 22:41 ` Richard Jones
2009-03-05 22:53 ` malc
2009-03-05 8:59 ` Richard Jones
2009-03-05 17:50 ` Raoul Duke
2009-03-05 8:17 ` Kuba Ober
2009-03-05 1:06 ` Jon Harrop
2009-03-05 9:09 ` Richard Jones
2009-03-05 20:44 ` Jon Harrop
2009-03-05 20:50 ` Jake Donham
2009-03-05 21:28 ` [Caml-list] OCaml's intermediate representations Jon Harrop
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=49AEF7EC.2000809@naughtydog.com \
--to=pal_engstad@naughtydog.com \
--cc=caml-list@yquem.inria.fr \
--cc=padator@wanadoo.fr \
/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