duplicating

If the functionality is useful enough, then it won't work because the maintenance is easier than duplicating their work.

De-duplicating might have a couple of downsides: 1) Not all good stories get taken up the first time.

So they often end up duplicating all controls on the steering wheel, how is that 'good design'?

Will anyone here be really surprised if it turns out ribosomes are duplicating machines designed by some alien race?

I may be mistaken but the issue the author is concerned with is de-duplicating breaking stories, not preventing the reposting of items from the long tail.

This is a terrible situation for developers (and ultimately users as dev effort is wasted duplicating things for each framework).

Of course, it's complemented by strong similarities to our layout and functionality, but there's something that seems more blatant about duplicating prose.

Reduce is certainly the better option with vectors (and maps?) if you write your own loop/recur you'll simply be duplicating the existing implementation.

In your case, you get to avoid duplicating the V8 team's work.

Someone makes those engines, and those who use them would bear the overhead of those who develop them wasting their time on duplicating work.

I suspect mostly because I started making music in an age when duplicating a CD was not possible and MP3 hadn't happened.

Then I'd start duplicating the sub modules and their interconnections in the core.

So, it depends on if Facebook doing "what Youtube already did" with regard to copyrighted material is duplicating their mistake, or if Facebook is engaging in an amoral "get away with it for as long as you can" situation.

It's left as an exercise for the reader whether the Apple watch is a product made by a UX company or by a company intent on duplicating the financial success of the ipad and iphone by cargo-culting the "create new device class" methods that worked before.