Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider the name modern #21

Open
rstacruz opened this issue Jan 5, 2016 · 6 comments
Open

Consider the name modern #21

rstacruz opened this issue Jan 5, 2016 · 6 comments

Comments

@rstacruz
Copy link
Contributor

rstacruz commented Jan 5, 2016

It sounds cool, no?

var fs = require('modern/fs')

The name is currently taken by an empty project, I'd assume it'd be possible to raise a dispute on it.

@jonathanong
Copy link
Contributor

sure. i just like mz because it's short!

@rstacruz
Copy link
Contributor Author

rstacruz commented Jan 5, 2016

haha, aye. I did get a "what the hell is an MZ" moment the first time I encountered it though

@haoxins
Copy link
Member

haoxins commented Jan 6, 2016

😄 I consider mz as normalize. +1 for a short name mz.

@jonathanong
Copy link
Contributor

well it's supposed to be short for "modernize" not "normalize" but yeah. i don't mind publishing it as both. lol. have one be an alias for the other.

@LinusU
Copy link
Contributor

LinusU commented Jan 6, 2016

Hmm, having both seems like extra maintenance without any real benefit. I don't even see exactly how it would be done; changing the name in package.json, running npm publish again and than changing back?

@rkmax
Copy link

rkmax commented Jun 12, 2016

I also like the mz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants