@MashedTech@lemmy.world to linuxmemes@lemmy.world • 1 year agoI'm probably going to get a lot of explanations in the commentslemmy.worldimagemessage-square145fedilinkarrow-up1739arrow-down150
arrow-up1689arrow-down1imageI'm probably going to get a lot of explanations in the commentslemmy.world@MashedTech@lemmy.world to linuxmemes@lemmy.world • 1 year agomessage-square145fedilink
minus-square@XTornado@lemmy.mllinkfedilink14•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@halva@discuss.tchncs.delinkfedilink1•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