-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[p5.js 2.0 RFC Proposal]: Pruning #7090
Comments
@nickmcintyre Just want to note that I am thinking about pruning many of the things you listed as well (particularly those that thinly wrap JS functions and p5.Table). I wouldn't necessarily remove the mobile events if at all possible and I would still keep the IO loading and http functions as they have their uses, perhaps with some API updates. Some idea around whether people are using p5.Table for example can greatly help with decision making here. |
One other WebGL feature that may be able to be pruned is the |
Increasing access
My sense is that this proposal affects maintainability and sustainability more than accessibility. That said, a smaller, more focused core library could be viewed as more accessible to beginners and contributors because there are fewer moving/interrelated parts.
Which types of changes would be made?
Most appropriate sub-area of p5.js?
What's the problem?
Many classes and functions aren't used widely, if at all. Others were ported directly from Processing and may no longer be needed given all the goodies in modern JavaScript. And a few are broken.
What's the solution?
Prune the following classes and functions. Maybe add some tutorials on data wrangling with arrays and objects.
Data
Events
The entire Acceleration section is broken on iOS without a workaround, so I suggest removing it.
IO
Pros (updated based on community comments)
Example list:
Cons (updated based on community comments)
TBD
Proposal status
Under review
The text was updated successfully, but these errors were encountered: