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-square46fedilinkarrow-up1238arrow-down1118
arrow-up1120arrow-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-square46fedilink
minus-squarePencilnoob@lemmy.worldOPlinkfedilinkEnglisharrow-up9arrow-down29·1 year agoBut you can’t see the code that runs those services, stores your settings, deploys your code, etc. Services are still a liability if they go away and your project depends on it
minus-squaremrpants@midwest.sociallinkfedilinkEnglisharrow-up23·1 year agoThey’re a completely different liability.
But you can’t see the code that runs those services, stores your settings, deploys your code, etc. Services are still a liability if they go away and your project depends on it
They’re a completely different liability.
deleted by creator