Azle Master Plan

[lastmjs]

• production-ready
  • API has not changed for a good length of time
  • npm package support
  • security reviews
  • mature dependencies
  • 5-10 production successful apps for 3-6 months
  • 100 total deployed canisters
  • robust property tests coverage of IC APIs
• broad npm package support
  • we support most/all of the most requested npm packages
  • Our core team/security council doesn't have outstanding package requests
  • Devs aren't clamoring for basic packages
• excellent documentation
  • The Azle Book filled out
  • JS Docs everywhere
  • nice website
  • video series
  • gorgeous errors
  • azle cli --help
  • LLM chatbot
  • Azle playground
  • Our own Discord channel
• core team/security council created
  • Find 5-10 Azle developers and make sure they have all of the support that they need from us
  • Decentralized the core Azle information, using Azle and developing Azle itself
• healthy contributor community
  • contributor documentation
  • issues organized into beginner, intermediate, advanced
  • public roadmap
  • ability to gather feedback quickly and comprehensively to prioritize features
• decentralized npm package deployment enabled and governed by core team/security council
  • Canister-controlled npm account (decentralized npm account)
  • Demergent Labs controls deployment from this canister, current npm package control given to canister
  • Core team/security council slowly given control with safeguards in place
  • Full core team/security council control
• Long-term JS engine chosen and implemented
  • wasmedge-quickjs?
  • V8?
  • SpiderMonkey?
  • our own Node/Deno Wasm project that gets buy-in from the developer community? Do we make this a stand-alone project that extends beyond ICP?
• Developer environment extremely slick
  • No more problems installing Azle
  • No more Podman/Docker
  • Wasm-based prebuilt dynamic binary