I partially agree. There is a high probability that people will still call
it LMMS; however, new people will often ask what LMMS stands for, and with
out a decent replacement set of names people will say Linux Multimedia
Studio. While we might say it no longer means anything, that aspect will
never fade until it's replaced. Heck if the issue is Giving it a single
name, then lets call it...
LeMMaS! :)
On Mon, Feb 3, 2014 at 4:00 PM, Vesa <dii....@nbl.fi> wrote:
> Speaking of Firefox...
>
> Firefox works because it's a single word, and a simple brand. It's also
> meaningful in a way - There used to be Mozilla web browser, and later on
> they made a separate project known as "Firefox", which was a faster,
> slimmer version of the Mozilla browser suite, and the "firefox"
> emphasized this "speed" aspect. Firefox later then became the main
> project and the old Mozilla browser died away, but the name stayed.
>
> Anyway, Firefox works because it's simple and metaphorical. But if it
> were a part of an acronym - like, if the browser were called "FFWB" or
> "MFWB" (Mozilla Firefox Web Browser) then it wouldn't make any sense to
> have the word "Firefox" in there.
>
> The metaphorical name and acronym are sort of incompatible, they have
> similar but conflicting purposes, and they sort of cancel each other
> out. An acronym reduces a technical, descriptive name into a more
> memorable and quick form, it's so that the users don't have to remember
> the parts that form the acronym. The acronym itself becomes the brand.
>
> Whereas in a metaphorical name, the name itself has the purpose of being
> cool and grabbing attention and being memorable. By compressing it down
> into an acronym, the metaphorical name loses it's effect, because people
> will only see the acronym, and especially if the acronym expands into a
> long string, no one will bother to remember what it actually stands for.
>
> Therefore, I'm starting to think that if we're going to keep the LMMS
> acronym, we might as well just call the software LMMS, without
> explaining the acronym in any way - it's just LMMS, that's it, because
> that's how people are going to call the software in the end anyway.
>
> Or, we go with a cool, simple, short metaphorical name (like Firefox),
> and ditch the LMMS and all other acronyms. Preferably it should be a
> single word, easy to remember - because there's no point in coming up
> with a cool name if people are just going to shorten it or collapse it
> to an acronym. Kind of defeats the purpose.
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> LMMS-devel mailing list
> LMMS-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>
>
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
