-
Notifications
You must be signed in to change notification settings - Fork 0
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
What should be the future of this library? #26
Comments
I've been considering turning this into my own personal library, but keep it public and open source for anyone to try it and see. That would give me more freedom to do whatever I want with this library, instead of adhering to ES standards I can still write polyfills as gists, or as PRs directed to Core-JS |
Yep, I realized I'm not qualified to make ES polyfills. Core-JS and a lot of proposals already do a good work at this. So I finally decided to merge my Useless-Math library with the Numeric object, and use helpers from core-js and myself. I'll start using ESM format, so I'll split everything in different folders and files. This will take a while |
I decided to rename the repo and library as "YAJSML" (Yet Another Javascript Math Library), because the library isn't very special, and I'm bad with names lol. Any suggestions for other names are appreciated |
New name: EsoMathJS, which stands for Esoteric Math |
FINAL NAME (I guess, lol) NTML.js |
(More info at #2 )
I'm concerned about the future of this library because I want to take it seriously, but I feel like I don't know if the direction I'm going is a good goal.
This library started like my "Useless-Math" repo, just a bunch of functions lying around, and there was no clear direction to take. Then I realized what direction I wanted to take, I wanted this to be a polyfill. But polyfills are usually meant to be used in websites, and this library is definitely not a good idea to use in a website, but I already stated that in the README disclaimer. So now I'm wondering in what should this be focused on?
The text was updated successfully, but these errors were encountered: