@[email protected] to [email protected] • 1 year agoI'm probably going to get a lot of explanations in the commentslemmy.worldmessage-square141fedilinkarrow-up1733
arrow-up1682imageI'm probably going to get a lot of explanations in the commentslemmy.world@[email protected] to [email protected] • 1 year agomessage-square141fedilink
minus-square@[email protected]linkfedilink14•1 year agoI mean doesn’t that come from Java naming conventions? Which then makes sense that it continued on Android… but Why did it end up on FlatPack!?
minus-squareTechognitolinkfedilinkEnglish3•1 year agoI will speculate to say that maybe someone looked at the java/android way and thought let’s just copy that. It’s the most plausible answer I can think of, without doing any research whatsoever
minus-square@[email protected]linkfedilink1•1 year agoIt’s a nice way to get around naming collisions.
I mean doesn’t that come from Java naming conventions? Which then makes sense that it continued on Android… but Why did it end up on FlatPack!?
I will speculate to say that maybe someone looked at the java/android way and thought let’s just copy that.
It’s the most plausible answer I can think of, without doing any research whatsoever
It’s a nice way to get around naming collisions.
Well yeah that’s true