Little question about KMMBridge: Should it be rena...
# touchlab-tools
r
Little question about KMMBridge: Should it be renamed to KMPBridge because KMM has been deprecated ?
j
Won't be able to pronounce it as Cambridge then πŸ˜ƒ
😲 2
☝️ 3
🀣 2
😒 1
k
Well, "1.0" is going out tomorrow. I "briefly" renamed it "KXCBridge", because it makes XCFrameworks, and the marketing folks were not excited. Changing names is bad. https://github.com/touchlab/KMMBridge/tree/kpg/kxcbridge.
πŸ‘ 1
But, I'm also pushing the "shared source instead" plan. We'll support both. Long story. https://touchlab.co/gitportal-for-kmp-tutorial-repo-ci-setup
πŸ‘ 1
k
Why git portal and not git lfs?
k
How would it work? Like a zip?
I mean, the "full" answer is the next feature of GitPortal, which is in progress, but curious how you'd use lfs?
k
Ah, I misunderstood - I thought you were using this gitportal
k
Nah. New "git portal"
k
Got it
So you get the benefits of submodules without the pain
k
Yes. Basically. There's more to it, but that's the basic pitch.
k
Whereas if you did git lfs it'd still just be about binaries and no source
k
Binaries are bad. No debugging or code visibility.
πŸ’― 1
k
But if we're in a monorepo for iOS + Android we can just keep chugging along
k
Oh, no. There's a whole different thing about that.
k
Does the git portal stuff change anything for publishing to SPM/Cocoapods? I'd assume not
k
That's the "other part" of GitPortal.
k
πŸ’―
I really wish I were at kotlinconf πŸ˜‚ 😭
k
It was fun, but I'm very happy to go home.
πŸ™Œ 1
@russhwolf gave the obvious answer and plan he had all along. "KMBridge". Same pronunciation, but avoids the "KMM" debacle.
πŸ‘ 2