Closed xnought closed 1 year ago
One consideration: falcon2 naturally implies a successor. However, it does not succeed the actual falcon name on npm (someone else owns that). Also there is plotly falcon which may also confuse things.
falcon-vis makes it distinct, but overrides the vega/falcon one. This may be fine, but not ideal.
perhaps something like falcon-data would differentiate things.
But also falcon2 is a one word, which is extremely simple and easy
@domoritz and @wchen6544, any thoughts or proclivities?
Fun thought that I'm starting to like: could be another extremely fast spaceship from another science fiction?
This could be a fun naming convention for a future family of packages that are also meant to do fast things on a ton of data.
Either as falcon2 (which I own on npm) or falcon-vis (which @domoritz own).
if we choose falcon2 then I'll @xnought move npm package ownership to @domoritz
I took up falcon2 on npm so I could originally import it on observable. I'm sure there is a better method, but that's how I imported it.
To discuss: which name will make more sense and stick? falcon2 or falcon-vis?