Yeah so there are many types of things that you want to abstract, avoiding code duplication is usually a good idea, also applies to small static things like primitives and well-defined components. The context of this article was more around the reuse of entire user experiences in a "Micro-frontend" application and how the DRY principle might not be a good idea for that use case.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hummm. DRY is about knowledge, not about code.
Code duplication can be even desirable, as you expose in the article. Knowledge duplication is another subject.
I would add a "0 question" => Does this duplication represent a unique concept? If the answer is no, leave the duplication in place.
Yeah so there are many types of things that you want to abstract, avoiding code duplication is usually a good idea, also applies to small static things like primitives and well-defined components. The context of this article was more around the reuse of entire user experiences in a "Micro-frontend" application and how the DRY principle might not be a good idea for that use case.