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

Proposal: Add discussion panel to repo for best practices discourse #1212

Open
superbuggy opened this issue Oct 24, 2023 · 0 comments
Open

Comments

@superbuggy
Copy link

superbuggy commented Oct 24, 2023

This is a feature request for the repository, and not for the Tone library itself.

I have come across some hurdles with Tone.js as a casual user where I've not been sure what the best practices are with Tone.js. I think there are some surmountable challenges to having productive discourse, listed as follows:

  1. Decidability of 'best' practices: stem from the flexibility of the Web Audio API and ToneJS, there are a lot of ways to do things. This perhaps could be framed in terms of patterns in a manner analogous to general programming design and practice.
  2. Synchronization of event systems: There can be framework-specific challenges with synchronizing the event system of the framework and with Tone.js, often ones that require a deep understanding of the framework itself, and often the toolchain and development environment that accompany it.
  3. Abstraction: Web Audio is an evolving API with some difficult design questions (ones well above my expertise) at its heart, often relating to the nature of an audio graph, its state, and the behavior of its components and event flows.

While I'm sure there are others, I think ordered discussion that accounts for these and other major themes could yield production discussion that benefits users and also helps them to be stronger developers in general. Developing with Tone and front-end frameworks has definitely posed challenges that often have lead me to a deeper understanding of the framework and have made me a better developer. This discussion could ideally enhance documentation as well.

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

No branches or pull requests

1 participant