4 ms·
Very nice, but it is confusing to name a library for using a language the same thing as that language. I suppose this is meant to be a temporary state of affair
by Philpax 1y ago
Very nice, but it is confusing to name a library for using a language the same thing as that language. I suppose this is meant to be a temporary state of affairs while Lua (the library) gets merged into Luerl, but I would have personally called it Luerl++ or such.
- davydog187 1y agoAuthor here! Luerl++ is not a valid module name :) More seriously, I considered alternate names, but settled on this because it was short, literal, and given that its in the context of Elixir, makes sense when using it. As you stated, the hope is to consolidate it into Luerl at some point
- antfarm 1y agoHave you considered "Luex", a nod to Luerl but with the typical Elixir suffix?
- davydog187 1y agoI have a personal mission to never name any libraries with the -ex prefix
- tommica 1y agoCurious, why?
- davydog187 1y agoEarly in the Elixir days, every library was named Thing-ex of ex-Thing. IMO this is really lazy in terms of naming and from a usage perspective, you get really tired of typing that out in code. I think we can do better
- antfarm 1y agoSuffixing a name with -ex often results in unique names, which helps filtering search results. I see a slight problem with name ending on an s though. Also, aren't you the author of jqex? ;)
- davydog187 1y agoTouche, although that is a 5 line utility. Filtering which search results? On hex.pm that’s irrelevant. On good “library name + elixir”
- deleted 1y ago[deleted]
- shakna 1y agoHumble appeal, because they'd win instantly: Please don't steal my useless project's name [0]. [0] https://luarocks.org/modules/shakna-israel/luaex https://luarocks.org/modules/shakna-israel/luaex
- toast0 1y agoWithin the BEAM ecosystem, consensus is to call something whatever2. If you wait long enough before replacing whatever2 with something that would be whatever3, you can go back to whatever (see pg -> pg2 -> pg)