From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: "'Sylvain Le Gall'" <sylvain@le-gall.net>, <caml-list@inria.fr>
Subject: RE: [Caml-list] Re: [Was: OCamlJit 2.0]
Date: Sat, 20 Nov 2010 18:51:22 -0000 [thread overview]
Message-ID: <04f001cb88e3$ee540ab0$cafc2010$@com> (raw)
In-Reply-To: <slrnieg2fs.r67.sylvain@gallu.homelinux.org>
Sylvain Le Gall:
> I doubt an old code, not written with multicore in mind is easily
> portable to multicore. So basically, the migration you are talking
> about
> is starting a new project that will replace one software/library by
> another.
Yes, the systems are kept loosely coupled during the transition so it is
more like a new project to supercede the old one than a gradual transition
between code bases. However, only the developers need be aware of this
distinction. From the point of view of everyone else in the company, the
implementation of a product is being modernized. Management get improved
productivity/maintainability. Sales get shiny new things. HR get to fire any
developers who resist (but most are assimilated ;-).
The avalanche happens when the cost of rewriting falls below the cost of
adding essential features to a legacy code base.
Cheers,
Jon.
next prev parent reply other threads:[~2010-11-20 18:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 14:52 OCamlJit 2.0 Benedikt Meurer
2010-11-16 17:07 ` [Caml-list] " bluestorm
2010-11-16 17:32 ` Benedikt Meurer
2010-11-17 8:44 ` Native toplevel? (was: OCamlJit 2.0) Alain Frisch
2010-11-17 10:46 ` Satoshi Ogasawara
2010-11-17 11:38 ` Sylvain Le Gall
2010-11-17 22:57 ` [Caml-list] Native toplevel? Wojciech Daniel Meyer
2010-11-18 16:49 ` [Caml-list] Native toplevel? (was: OCamlJit 2.0) Ashish Agarwal
2010-11-19 18:09 ` David MENTRE
2010-11-19 18:24 ` Hezekiah M. Carty
2010-11-19 18:30 ` Ashish Agarwal
2010-11-19 18:42 ` Benedikt Meurer
2010-11-20 11:49 ` Jon Harrop
2010-11-18 18:19 ` Benedikt Meurer
[not found] ` <2025993285.616104.1290144569061.JavaMail.root@zmbs4.inria.fr>
2010-11-19 10:02 ` [Caml-list] Re: Native toplevel? Fabrice Le Fessant
2010-11-19 19:16 ` Benedikt Meurer
2010-11-19 18:43 ` [Caml-list] OCamlJit 2.0 Yoann Padioleau
2010-11-19 19:10 ` Benedikt Meurer
2010-11-20 15:59 ` Yoann Padioleau
2010-11-19 19:46 ` Dario Teixeira
2010-11-19 20:20 ` Yoann Padioleau
2010-11-20 15:19 ` [Was: OCamlJit 2.0] Vincent Balat
2010-11-20 15:42 ` [Caml-list] " Benedikt Meurer
2010-11-20 16:10 ` Yoann Padioleau
2010-11-20 16:25 ` Benedikt Meurer
2010-11-20 17:35 ` Yoann Padioleau
2010-11-20 17:08 ` Jon Harrop
2010-11-20 17:37 ` Yoann Padioleau
2010-11-20 17:48 ` Sylvain Le Gall
2010-11-20 18:51 ` Jon Harrop [this message]
2010-11-20 18:05 ` [Caml-list] " Jon Harrop
2010-11-20 17:15 ` Gerd Stolpmann
2010-11-23 2:09 ` Elias Gabriel Amaral da Silva
2010-11-24 7:20 ` [Caml-list] OCamlJit 2.0 Alain Frisch
2010-11-24 7:59 ` Yoann Padioleau
2010-11-24 9:04 ` Compiling to Javascript Jerome Vouillon
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='04f001cb88e3$ee540ab0$cafc2010$@com' \
--to=jonathandeanharrop@googlemail.com \
--cc=caml-list@inria.fr \
--cc=sylvain@le-gall.net \
/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).