▲ 546 ▼ Which side are you? Javascript or Typescript (i.postimg.cc) submitted 3 years ago by mastermind@lemm.ee to c/programmer_humor@programming.dev 224 comments fedilink hide all child comments
[–] dragnucs@lemmy.ml -2 points 3 years ago (1 child) I refuse to use it because it is backed by Microsoft. permalink fedilink source parent hideshow 2 child comments replies: [–] jpeps@lemmy.world 4 points 3 years ago (2 children) I can understand that. Does it's open source status not change anything for you? permalink fedilink source parent hideshow 4 child comments replies: [–] dragnucs@lemmy.ml -1 points 3 years ago They have a vert high chance of pulling slack. permalink fedilink source parent [–] Knusper@feddit.de -2 points 3 years ago (1 child) If it's dumped under an open-source license, but still developed exclusively by one corporation, they can swap out that license pretty easily. permalink fedilink source parent hideshow 2 child comments replies: [–] jpeps@lemmy.world 2 points 3 years ago (1 child) For what? If they took it away, the source code would still be there if someone wanted to fork it. Not to mention removing TypeScript from an application is relatively trivial. permalink fedilink source parent hideshow 2 child comments replies: [–] Knusper@feddit.de 0 points 3 years ago They're not that dumb, to just pull it completely. That would obviously result in a successful fork. Companies usually start with e.g. the BUSL, so source-available but proprietary restrictions. For TypeScript/Microsoft, I could imagine some variation of their EEE playbook. But really, the whole point of avoiding Microsoft et al, is that I don't want to think about, how they could fuck this whole thing up. They've proven quite creative in this regard for as long as they've existed. permalink fedilink source parent
[–] jpeps@lemmy.world 4 points 3 years ago (2 children) I can understand that. Does it's open source status not change anything for you? permalink fedilink source parent hideshow 4 child comments replies: [–] dragnucs@lemmy.ml -1 points 3 years ago They have a vert high chance of pulling slack. permalink fedilink source parent [–] Knusper@feddit.de -2 points 3 years ago (1 child) If it's dumped under an open-source license, but still developed exclusively by one corporation, they can swap out that license pretty easily. permalink fedilink source parent hideshow 2 child comments replies: [–] jpeps@lemmy.world 2 points 3 years ago (1 child) For what? If they took it away, the source code would still be there if someone wanted to fork it. Not to mention removing TypeScript from an application is relatively trivial. permalink fedilink source parent hideshow 2 child comments replies: [–] Knusper@feddit.de 0 points 3 years ago They're not that dumb, to just pull it completely. That would obviously result in a successful fork. Companies usually start with e.g. the BUSL, so source-available but proprietary restrictions. For TypeScript/Microsoft, I could imagine some variation of their EEE playbook. But really, the whole point of avoiding Microsoft et al, is that I don't want to think about, how they could fuck this whole thing up. They've proven quite creative in this regard for as long as they've existed. permalink fedilink source parent
[–] dragnucs@lemmy.ml -1 points 3 years ago They have a vert high chance of pulling slack. permalink fedilink source parent
[–] Knusper@feddit.de -2 points 3 years ago (1 child) If it's dumped under an open-source license, but still developed exclusively by one corporation, they can swap out that license pretty easily. permalink fedilink source parent hideshow 2 child comments replies: [–] jpeps@lemmy.world 2 points 3 years ago (1 child) For what? If they took it away, the source code would still be there if someone wanted to fork it. Not to mention removing TypeScript from an application is relatively trivial. permalink fedilink source parent hideshow 2 child comments replies: [–] Knusper@feddit.de 0 points 3 years ago They're not that dumb, to just pull it completely. That would obviously result in a successful fork. Companies usually start with e.g. the BUSL, so source-available but proprietary restrictions. For TypeScript/Microsoft, I could imagine some variation of their EEE playbook. But really, the whole point of avoiding Microsoft et al, is that I don't want to think about, how they could fuck this whole thing up. They've proven quite creative in this regard for as long as they've existed. permalink fedilink source parent
[–] jpeps@lemmy.world 2 points 3 years ago (1 child) For what? If they took it away, the source code would still be there if someone wanted to fork it. Not to mention removing TypeScript from an application is relatively trivial. permalink fedilink source parent hideshow 2 child comments replies: [–] Knusper@feddit.de 0 points 3 years ago They're not that dumb, to just pull it completely. That would obviously result in a successful fork. Companies usually start with e.g. the BUSL, so source-available but proprietary restrictions. For TypeScript/Microsoft, I could imagine some variation of their EEE playbook. But really, the whole point of avoiding Microsoft et al, is that I don't want to think about, how they could fuck this whole thing up. They've proven quite creative in this regard for as long as they've existed. permalink fedilink source parent
[–] Knusper@feddit.de 0 points 3 years ago They're not that dumb, to just pull it completely. That would obviously result in a successful fork. Companies usually start with e.g. the BUSL, so source-available but proprietary restrictions. For TypeScript/Microsoft, I could imagine some variation of their EEE playbook. But really, the whole point of avoiding Microsoft et al, is that I don't want to think about, how they could fuck this whole thing up. They've proven quite creative in this regard for as long as they've existed. permalink fedilink source parent