3 ms·
I think the problems lie in reimplementing something with disregard for the experiences gathered when it was implemented the first time. There are plenty of tim
by pyre 17y ago
I think the problems lie in reimplementing something with disregard for the experiences gathered when it was implemented the first time. There are plenty of times where solutions a wiped up to age-old problems that only work in the most common of cases, and cause huge headaches when the edge cases are hit. On the other hand, mature solutions with wide user-bases have already run into and solved these problems.
Basically, there's no point in re-inventing the wheel unless you're meaning to improve the existing implementation or at least bring something new to the table. Too many times things are re-implemented and labelled as 'new and improved' even though they are a decided step backwards.
All of that said, I think that original statement was meant to be a push-back against the prevailing 'wisdom' that Perl is dead and that you should really be onto something like Python or Ruby like all of the 'cool kids' are doing. (i.e. "Don't discount Perl, it has many solutions to offer you.")