Pencilnoob@lemmy.world to Programmer Humor@lemmy.mlEnglish · 2 years 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-square69fedilinkarrow-up1451arrow-down1166
arrow-up1285arrow-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 · 2 years agomessage-square69fedilink
minus-squarePencilnoob@lemmy.worldOPlinkfedilinkEnglisharrow-up9arrow-down31·2 years 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-up24·2 years 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
deleted by creator