You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A deeper understanding of the Soroban VM is need for building a better, more efficient SDK.
The Build your own SDK doc, in my opinion, lacks critical information for SDK builders, like the design decisions behind Soroban VM for instance
Formulated in a way that exposes clear points on how to use the VM. For instance, reading Why doesn't Soroban use a Jit leads to the conclusion that wen building an SDK, all the heavy work (like allocating memory) shall be done host side not guest side.
salaheldinsoliman
changed the title
Add instructions on how to use the VM when building and SDK
Add instructions on how to use the VM when building an SDK
Sep 19, 2024
What problem does your feature solve?
A deeper understanding of the Soroban VM is need for building a better, more efficient SDK.
The
Build your own SDK
doc, in my opinion, lacks critical information for SDK builders, like the design decisions behind Soroban VM for instanceWhat would you like to see?
Precious info like in: https://stellar.org/blog/developers/why-doesnt-soroban-use-a-jit
And https://stellar.org/blog/developers/project-jump-cannon-choosing-wasm
Formulated in a way that exposes clear points on how to use the VM. For instance, reading
Why doesn't Soroban use a Jit
leads to the conclusion that wen building an SDK, all the heavy work (like allocating memory) shall be done host side not guest side.What alternatives are there?
Discord is always there :) but precious convos as:
https://discordapp.com/channels/897514728459468821/1067534037310255225/1273873467699105907
Usually get lost
The text was updated successfully, but these errors were encountered: