Suppose:

• Your company has been successfully selling a big, expensive product to big corporations for twenty years.
• This product has Perl embedded in it. To allow customers -- and your Consulting Division -- to extend and customize the product.
• This product runs on ten different operating systems.
• This product has over a million lines of code.
• Your Consulting Division has 100 consultants. They have also written over a million lines of code.
• Worldwide, you have 1000 users of your product who routinely customize it with Perl. They have written over a million lines of code.

Note that your customers and consultants have relatively modest scripting requirements and are far more interested in their business domain than in Perl vs Python language debates.

How much would it cost to switch from Perl to Python, say?

• The cost of porting, testing and packaging a new language into your product (and removing Perl) across ten operating systems.
• The cost of rewriting a million lines of working code in your product.
• The cost to your Consulting Division of rewriting a million lines of working code. Consultants are on a "90% billable hours" KPI. Customers will not pay Consultants to rewrite working code.
• The cost of retraining your developers in a new language. Maybe a one week training course for each person. Then wait six months before they become truly fluent in the new language.
• The cost of retraining 100 Consultants in a new language. Customers will not pay for Consultants to attend training courses.
• The cost to your customers of having to rewrite their working customizations in a new language.
• The cost to your customers of having to train their staff in a new programming language.
• The cost of bugs introduced in the rewrites.
• The opportunity cost to you and your customers of not doing other things in your business domain because you are spending time and resources on rewriting something that already works.
• The ill-will you suffer from your customers because they don't want to spend time and money training their staff in a new programming language and rewriting working code. They'd much rather focus on their business domain, not a programming language.

See also: On not rewriting by Joel Spolsky

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.