Pluralize and performance about pluralize

[blakeembrey]

A ternary will always be quicker than a bunch of regexp tests. However, this is not just about performance but also library weight (e.g. 2kb) and plural accuracy. If you know the plurals you want to use in advance, there's doesn't seem to be a need to add this as a dependency.

[carpben]

At the moment there are only 2 strings which needs to be pluralized, and we know them in advance. But we do inject these fields from the back-end, and we try to keep our front-end app somewhat independent, and hide the specific details from it. So in our React App we simply have a general variable, and though it can only get 2 specific values from the back-end, it will be a bit strange to treat it as a general string all along, and then to pluralize it by handling only the two specific cases.

[blakeembrey]

I'm not really sure I follow, but you're welcome to do it whichever way you prefer. I can't prescribe how you build your front-end, but a ternary is certainly faster and lighter weight than using a library. With that said, it's unlikely you'll notice a difference in any case unless you're seriously trying to cut down on bytes in your web app (but it doesn't sound like this is the case).