jlouis/fuse

Project name isn't great

kxepal opened this issue · 5 comments

kxepal commented

I'll open this issue because it's too oblivious (:

Reading announce on erlang-questions@ I wondering how all of those text is related to FUSE and actually, the first and only association was: "Isn't this Erlang bindings to FUSE?" Like fuserl is. Google agrees with me on that: any "{language_name} fuse" request returns list of FUSE bindings on the top, so it would be hard to find your library (though it's looks very useful) like his name will confuse people who doesn't know about.

So may be it's a little bit late for name changes when 1.0.0 is released, but still is it possible to pick some more better name for the project?

jlouis commented

I had a long thought about this when deciding on the name, exactly because of FUSE. But on the other hand, I hope people will manage to discriminate different tools since the context is rather different after all.

It isn't the first point in time where we have name clashes, and while I thought about it, I think I'll keep the current name for now. I'll add a notice in the README pointing to fuserl though so people get guided.

laheadle commented

Any reason this is still open?

jlouis commented

Well, FUSE isn't gone yet :)

paulo-ferraz-oliveira commented

For me, Google'ing for "erlang fuse" yield first result as "https://github.com/jlouis/fuse", but I know Google is biased 😄.

jlouis commented

Ok, at least one issue can be closed today!

  • 👍2