[haiku-development] Re: Name the package manager "Software Valet"
- From: Dario Casalinuovo <b.vitruvio@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 4 Jun 2013 13:22:55 +0200
I don't think the software valet name is self-descriptive at all. Maybe it
could be for English speaking people, but i was just thinking on how it
could be translated to Italian, and i ended up that it would
be misunderstood/confusing, for example valet is pretty similar to
"valletta" which usually refers to assistant/dancers girls in tv shows (and
similar things). In some other meanings it could be intended as the
masculine "valletto", which become from the middle ages and was referred to
the knight squire (this is a meaning in disuse, but you can find it already
in dictionaries).
Anyway, assuming that the name of the app will be translated in every
language (just as it's done in linux distros), for a Italian the literal
translation "Valletta/o del software" is not in any way cool or
descriptive, and could easily make confusion.
Not that the Italian language is something which can be used as meter,
since it's used only by 60 millions of people, but in the official site i
read "Haiku is free from unneeded complexities", well for me naming the
package manager, software valet is a unneeded complexity in all cases
(translated or not).
I don't know in other Latin languages how it's perceived, but i presume for
languages with totally different roots, grammar and alphabet like Chinese,
Indian, Arabic (...), the name "Package Manager" is just the better choice
as it's the more common way to name it in the world.
And i think it would be also easier for them to translate it.
And it's also funny for me to think to a newbie which ask "hey guys where's
the package manager?" and one reply "You can run it from
Deskbar->apps->software valet.."
maybe it's quicker, simpler and effective to call it with his name? : )
Best Regards
On Tue, Jun 4, 2013 at 11:04 AM, Stephan Aßmus <superstippi@xxxxxx> wrote:
> Hi,
>
> Am 04.06.2013 um 10:51 schrieb "Chris Peel" <chrispeel.mail@xxxxxxxxx>:
> > Ok, so I'm now straying off-topic here and I should create a new thread
> (maybe one exists already) - but crucially then, what is Haiku if its not a
> continuation of BeOS?
> >
> > Without a clear goal, there's a danger it will either meander or will
> simply be seen as a another Linux distro/clone.
> >
> > For me, I was expecting Haiku to continue the BeOS ethic of a
> minimalist interface (and by that I mean the HCI, not the GUI - that is, I
> don't mean a flat Metro style look - just the lovely simple nature of
> having the right menu options where you expect them) but to then support
> modern functionality (HMTL5, etc.) so that it's still usable in the 2010s.
>
> I don't see how/where anything that I wrote and which you are replying to,
> would contradict anything that you have written. For example, where did I
> say Haiku would not be a continuation of BeOS? I specifically used the
> metaphor "path" which implies continuation. All that being said, I am no
> authority. Why would you take anything I say to mean anything definite or
> official about what Haiku is or is not supposed to be. What Haiku is, is
> defined by the code its composed of. The code that gets written or changed
> will likely be influenced by smart and appealing things people write on the
> mailing lists or elsewhere. But regardless Haiku is defined by its code and
> of course the community as a whole if you consider the "project" versus the
> "product". It is shaped by consensus. What I wrote was just my contribution
> to influence the consensus, don't take it for anything else.
>
> Best regards,
> -Stephan
>
> > On Tue, Jun 4, 2013 at 11:39 AM, Stephan Aßmus <superstippi@xxxxxx>
> wrote:
> > Am 04.06.2013 um 10:03 schrieb Marcus Jacob <rossi@xxxxxxxxxxxxxxx>:
> >
> > > On 04.06.2013, at 08:05, "Chris Peel" <chrispeel.mail@xxxxxxxxx>
> wrote:
> > >
> > >> Raises an interesting debate about what Haiku is meant to be.
> > >>
> > >> If it's a homage to BeOS, just as AmigaOS 4 is to AmigaOS 3, then
> you should stick with Software Valet as the name.
> > >
> > > +1
> > >
> > > Afaik I thought Haiku R1 is more or less a reimplementation of BeOS R5.
> > >
> > > Otherwise other "defects" in the APIs could be fixed and binary
> compatible could also be dropped.
> >
> > Doesn't make much sense to me. Fixing defects in the APIs or introducing
> new ones doesn't mean binary compatibility has to be dropped. At the same
> time, if Haiku couldn't eventually do those things, at least progress in
> the APIs, what interesting would it be? Just BeOS R5 on concurrent hardware
> and stay like that forever? No thanks. Haiku R1 is just one step along the
> path. Reimplementing R5 was a goal everyone could focus on for the time
> being. Nothing more, nothing less. And it's not like we are way past
> "reimplementing" in certain crucial areas. The whole package management is
> something BeOS never had.
> >
> > Best regards,
> > -Stephan
> >
>
>
Other related posts:
