zippy@lemmy.zip to Linux@lemmy.ml · 11 hours agoGIMP rebranding as WLBR?gitlab.gnome.orgexternal-linkmessage-square124linkfedilinkarrow-up1125arrow-down16
arrow-up1119arrow-down1external-linkGIMP rebranding as WLBR?gitlab.gnome.orgzippy@lemmy.zip to Linux@lemmy.ml · 11 hours agomessage-square124linkfedilink
minus-squareMrSoup@lemmy.ziplinkfedilinkarrow-up38·9 hours agoWhy not just Wilber? Just like the mascot.
minus-squareslartibartfast141@piefed.ziplinkfedilinkEnglisharrow-up38·9 hours agoThe Linux community can’t let an opportunity for an acronym to go to waste. Even more so for a backronym.
minus-squarewiki_me@lemmy.mllinkfedilinkEnglisharrow-up3·3 hours agoIt’s another case of OSPNS - Open source projects names sucking .
minus-squareeleijeep@piefed.sociallinkfedilinkEnglisharrow-up12·9 hours agoCould have had the recursive acronym KINGIMP (KINGIMP Is Not GIMP) smdh
minus-squaregrue@lemmy.worldlinkfedilinkarrow-up2·5 hours agoThat’s for the fork with a UI implemented in Qt.
minus-squaresp3ctr4l@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up4·7 hours agoPerhaps ‘WiLBeR’ would be a compromise? Its … basically following what I’m going to call ‘GLaDOS case’ rules. ??? Just sort of seems closer to the kind of silly spellings of robot names in a fair deal of movies and such?
Why not just Wilber? Just like the mascot.
The Linux community can’t let an opportunity for an acronym to go to waste. Even more so for a backronym.
It’s another case of OSPNS - Open source projects names sucking .
Could have had the recursive acronym KINGIMP (KINGIMP Is Not GIMP) smdh
That’s for the fork with a UI implemented in Qt.
Perhaps ‘WiLBeR’ would be a compromise?
Its … basically following what I’m going to call ‘GLaDOS case’ rules.
???
Just sort of seems closer to the kind of silly spellings of robot names in a fair deal of movies and such?
GNU Wilber