News for hackers. Stuff that matters.
Re:When you combine two things that are close, but not the same by throwaway2037 on Thursday April 13, 2023 @10:43PM (#35564933)
I understand your sentiment, but this line:

    When you dedupe, you've also given birth to a new abstraction, and those don't come for free.
It feels like you can write the inverse with equivalent impact, e.g., code duplication doesn't come for free.
Re:When you combine two things that are close, but not the same by maxbond on Friday April 14, 2023 @02:08AM (#35566059)
What's the cost? A slightly bigger binary & codebase? It seems like it's close to free to me. Am I missing a cost? Or are these costs bigger than I'm assigning them?
Re:When you combine two things that are close, but not the same by nextaccountic on Friday April 14, 2023 @02:23AM (#35566152)
> What's the cost?

The cost is exactly what is pointed in the original tweet:

> a requirement to keep two separate things aligned through future changes is an “invisible constraint” that is quite likely to cause problems eventually

Code changes, and if those two identical or similar pieces of code are likely to change together, now whenever you change one you have the cognitive load to also change the other, or risk having them go out of sync.

Of course, when the two pieces of similar code aren't likely to be changed together, they should be kept separated

Re:When you combine two things that are close, but not the same by maxbond on Friday April 14, 2023 @02:32AM (#35566206)
For sure. Most of the time when I copy-paste code from one place to another, a change in one place doesn't imply a change in the other. I certainly have seen that happen though.
Re:When you combine two things that are close, but not the same by shakna on Friday April 14, 2023 @10:40AM (#35570062)
* * *