Pencilnoob@lemmy.world to Programmer Humor@lemmy.mlEnglish · 1 year ago"First remove the closed source vendor lock in from your own codebase before checking for license issues in your neighbor's codebase" Engineerings 5:33lemmy.worldimagemessage-square73fedilinkarrow-up1442arrow-down1163
arrow-up1279arrow-down1image"First remove the closed source vendor lock in from your own codebase before checking for license issues in your neighbor's codebase" Engineerings 5:33lemmy.worldPencilnoob@lemmy.world to Programmer Humor@lemmy.mlEnglish · 1 year agomessage-square73fedilink
minus-squareHot Saucerman@lemmy.mllinkfedilinkEnglisharrow-up10arrow-down2·edit-21 year agoY’all are fundamentally talking about different things and are failing to see why they are different. Vendor lock in from proprietary software is not the same thing as vendor lock in from using vendors hardware. Both are bad, but they are not the same, and conflating the two is misunderstanding the point. Just like the original meme misunderstood the point.
Y’all are fundamentally talking about different things and are failing to see why they are different.
Vendor lock in from proprietary software is not the same thing as vendor lock in from using vendors hardware.
Both are bad, but they are not the same, and conflating the two is misunderstanding the point. Just like the original meme misunderstood the point.