[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: parsing markup with Perl
The stackoverflow heading is so misleading. The heading talks about regular expressions and his evidence is a Perl script. He may as well say he can parse html using plus and minus on the same evidence! What a crock. Fill in your usual boilerplate on desperate Perl hacker here. About 15 years ago I had a job working on the Perl scripts of one of the big 3 legal publishers here. They had 3 people trying to find bugs and two fixing them and one manager. They had unreadable code and it was driving them into the ground. My takeaway was that Perl as it stood then required infeasibly much commenting to be maintainable: it is hacker friendly which means you need extra discipline: code reviews and comment audits. (The very things you probably were trying to avoid needing by using a scripting language, which you bought into because you thought you were getting flexible and agile.) It was a bad gig. The writing was on the wall. In fact that company did get driven into the ground: they were bought up by my current employer. And I now find myself working on new systems for those same products. I am probably not at liberty to divulge the dolorous history of Perl here since then. They did move text and event processing out to Omnimark leaving the higher shell functions in Perl. Typical 1990s. I think I can say that our recent implementations certainly don't use Perl. The issue for corporate coding is not whether a well-managed disciplined group of experienced programmers can turn out maintainable Perl (or any language) code with the benefit of hindsight, but how fast the code sinks into maintainability as soon as someone drips the ball (wrong design, wrong review process, wrong experience, wrong texting, etc). I don't think Perl has a good track record, based on what I have seen at least. Imho it is too risky. I am finding the combination of PowerShell and 'xslt2 pretty good at the moment, as an alternative. Actually, the split where XSLT2 does transformations and the shell/job queue does higher level operations helps a separation of concerns. Rick On 08/02/2014 5:20 AM, "Ihe Onwuka" <ihe.onwuka@gmail.com> wrote:
Fantabulous.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|