7 ms·

This has a high risk of being confused with PixiJS, which is often just referred to as pixi, and is a popular 2D WebGL renderer. https://github.com/pixijs/pixi

This has a high risk of being confused with PixiJS, which is often just referred to as pixi, and is a popular 2D WebGL renderer. https://github.com/pixijs/pixijs https://github.com/pixijs/pixijs This project is likely to get drowned out by pixi search results when its users try to Google anything related to it.

hutzlibu 5y ago
Yes, I also just came here to ask a question about pixijs ...
hnlmorg 5y ago
It's almost impossible to come up with names these days due to the massive amount of software released every year. It's so bad that I automatically include the language name as well as the framework name in any search I do. In this instance the Nim and JS libraries have different names (and even different spellings of the common subset) so I don't see an issue.
- vanderZwan 5y ago
  > In this instance the Nim and JS libraries have different names They're both named "Pixie" and they're both graphics libraries. I assume you meant something else than what you literally said, but I'm not sure what
  - ShangSixtyTwo 5y ago
    "Pixi" != "Pixie"
    - hithereagain 5y ago
      But "Pixi" == "Pixie" when evaluated by humans
      - hnlmorg 5y ago
        It's called PixiJS though.
        MadcapJake 5y ago
        The namespace is pixi which is what people will be searching.
        hnlmorg 5y ago
        Then they're searching wrong because that's not the name of the package. Plus, as I opened with, people should be including their language name as part of the search query by default regardless of the framework's name. It seems absurd to me that developers are too lazy to add one extra keyword to their search to ensure they get specific results, yet are happy to moan about maintainers not putting enough effort in to avoid namespace collisions in a finite pool of usable project names (and particularly when the project names here are literally different). This strikes me as bad workmen blaming their tools; you have a bad search etiquette and are then passing the buck onto the maintainers to fix. Sorry if that seams harsh but naming things is really hard but adding `nim` into your search query is really easy. To me it is pretty clear cut where this problem should be solved.
    - MadcapJake 5y ago
      The levenshtein distance is still just 1 insertion so search results will likely be mixed.
- chmod775 5y ago
  I explained the issue. In case you need to see it, here's a screenshot of me googling for something pixie related (that shows up in its README.md), but getting pixi.js results. https://i.imgur.com/9pJuaJO.png https://i.imgur.com/9pJuaJO.png
  - hnlmorg 5y ago
    > I explained the issue. In case you need to see it That's an awful lot of sass from someone who didn't bother to read my post: 1. You're not using the language name in your search query like I suggested one should. So your example is moot. 2. You're still being highly critical about something that is awfully hard to get right. Naming projects is one of the hardest things you can do to a project. Firefox went through 2 naming collisions before they landed on Firefox. As an open source contributor myself I frequently get people say "Your name is used by this thing over here too" despite me spending literally hours going through multiple different name options and Googling them to see if they have a presence (search engines aren't always good for checking this stuff by the way). When there are hundreds of thousands of people creating software each month, you quickly run out of phonetics to use. While naming might seem like an infinitely large namespace, in practice there's only a finite number of names out there yet a literal infinity of projects due to new ones popping up all the time. So collisions aren't just inevitable, they're going to become more frequent too. This is why open source frameworks for different languages where the spellings differ is fine in my opinion because you should always include the language you're targeting in your search query for more accurate results anyway. Sometimes I think people just like to throw namespace collisions as a criticism on HN because they're too lazy to research the framework properly but still want to appear knowledgeable to everyone else. It's literally the lowest effort critique one can make on a project.
    - chmod775 5y ago
      I pointed this out because pixi.js was the first thing I thought off when I read the title of this post. Others have pointed out they made the same association. Do you really want to pretend with all your might that naming your graphics library after the same creature as another graphics library is a good idea? Really? Coincidentally I just named a rendering library for WebGL a few days ago and it's already the first result on google. Naming projects isn't that hard if you don't want a 3-6 letter name. There's only so many possible combinations of five characters. You'd think software developers of all people would understand that and maybe stop giving their projects short names that look like acronyms and convey literally no meaning. The easiest way is to pick a longer descriptive name with a good acronym. If your project becomes popular, it'll become known by that acronym. Most 2 word combinations aren't taken either.
tokai 5y ago
Its not a real HN library thread without unjustified irl-namespace collision claims.
christophilus 5y ago
I read the title, and thought pixijs had moved to nim + webassembly.

hutzlibu 5y ago

Yes, I also just came here to ask a question about pixijs ...

hnlmorg 5y ago

It's almost impossible to come up with names these days due to the massive amount of software released every year. It's so bad that I automatically include the language name as well as the framework name in any search I do. In this instance the Nim and JS libraries have different names (and even different spellings of the common subset) so I don't see an issue.

vanderZwan 5y ago
> In this instance the Nim and JS libraries have different names They're both named "Pixie" and they're both graphics libraries. I assume you meant something else than what you literally said, but I'm not sure what
- ShangSixtyTwo 5y ago
  "Pixi" != "Pixie"
  - hithereagain 5y ago
    But "Pixi" == "Pixie" when evaluated by humans
    - hnlmorg 5y ago
      It's called PixiJS though.
      - MadcapJake 5y ago
        The namespace is pixi which is what people will be searching.
        hnlmorg 5y ago
        Then they're searching wrong because that's not the name of the package. Plus, as I opened with, people should be including their language name as part of the search query by default regardless of the framework's name. It seems absurd to me that developers are too lazy to add one extra keyword to their search to ensure they get specific results, yet are happy to moan about maintainers not putting enough effort in to avoid namespace collisions in a finite pool of usable project names (and particularly when the project names here are literally different). This strikes me as bad workmen blaming their tools; you have a bad search etiquette and are then passing the buck onto the maintainers to fix. Sorry if that seams harsh but naming things is really hard but adding `nim` into your search query is really easy. To me it is pretty clear cut where this problem should be solved.
  - MadcapJake 5y ago
    The levenshtein distance is still just 1 insertion so search results will likely be mixed.
chmod775 5y ago
I explained the issue. In case you need to see it, here's a screenshot of me googling for something pixie related (that shows up in its README.md), but getting pixi.js results. https://i.imgur.com/9pJuaJO.png https://i.imgur.com/9pJuaJO.png
- hnlmorg 5y ago
  > I explained the issue. In case you need to see it That's an awful lot of sass from someone who didn't bother to read my post: 1. You're not using the language name in your search query like I suggested one should. So your example is moot. 2. You're still being highly critical about something that is awfully hard to get right. Naming projects is one of the hardest things you can do to a project. Firefox went through 2 naming collisions before they landed on Firefox. As an open source contributor myself I frequently get people say "Your name is used by this thing over here too" despite me spending literally hours going through multiple different name options and Googling them to see if they have a presence (search engines aren't always good for checking this stuff by the way). When there are hundreds of thousands of people creating software each month, you quickly run out of phonetics to use. While naming might seem like an infinitely large namespace, in practice there's only a finite number of names out there yet a literal infinity of projects due to new ones popping up all the time. So collisions aren't just inevitable, they're going to become more frequent too. This is why open source frameworks for different languages where the spellings differ is fine in my opinion because you should always include the language you're targeting in your search query for more accurate results anyway. Sometimes I think people just like to throw namespace collisions as a criticism on HN because they're too lazy to research the framework properly but still want to appear knowledgeable to everyone else. It's literally the lowest effort critique one can make on a project.
  - chmod775 5y ago
    I pointed this out because pixi.js was the first thing I thought off when I read the title of this post. Others have pointed out they made the same association. Do you really want to pretend with all your might that naming your graphics library after the same creature as another graphics library is a good idea? Really? Coincidentally I just named a rendering library for WebGL a few days ago and it's already the first result on google. Naming projects isn't that hard if you don't want a 3-6 letter name. There's only so many possible combinations of five characters. You'd think software developers of all people would understand that and maybe stop giving their projects short names that look like acronyms and convey literally no meaning. The easiest way is to pick a longer descriptive name with a good acronym. If your project becomes popular, it'll become known by that acronym. Most 2 word combinations aren't taken either.

tokai 5y ago

Its not a real HN library thread without unjustified irl-namespace collision claims.

christophilus 5y ago

I read the title, and thought pixijs had moved to nim + webassembly.