I’ve read through this forum post and its comments multiple times, but I’m still unclear about the concept of the “minimalistic playground in the browser.” Here are some specific questions and concerns:
1. What is the problem you are trying to solve with the “minimalistic playground in the browser”?
2. Who are the target users of this playground?
3. How is this playground going to help these users?
4. What can be done with this playground that couldn’t be done with a Remix plugin?
5. Why is this playground a prerequisite for creating a Hardhat plugin? I understand the value of creating a Hardhat or Remix plugin, but I’m struggling to see the value of the “minimalistic playground in the browser”.
6. Why not create a plugin from the start? Why is there a need to create a new online editor? Past feedback suggested avoiding new tools unless there’s a strong justification. Did I miss an explanation?
7. Couldn’t this also be achieved through a Remix plugin?
8. Are you sure that their recommendation was to create a “minimalistic playground in the browser”? The last feedback I read suggested avoiding new tools initially and focusing on plugins instead.
9. Did the team request this? Will they be able to use your first delivery for this purpose?
Let’s dive into the technical details because I would like to understand better how you are going to tackle this:
10. Could you elaborate on this replacement process? Which kind of node will this playground work against?
- Will it work against a Frontier-based node?
- Will you contribute to the ethink project and built on top of it?
- Will you fork the
@acala-network/eth-rpc-adapterand adapt it for your own needs? - Will you create a custom solution?
- Something else… Another solution that I don’t know about, or one that’s currently under development, perhaps?
What trade-offs have you considered, and which path will you take to:
?