Big Bag Of Ideas

[Sam Gammon (sgammon)]

In no particular order:

• Server could support OpenTelemetry via a built-in logback adapter
• Exposing server endpoints / dashboard like Micronaut
• We should add file logging (speaking of logback adapters) -- ideally for the server and not the whole runtime
• Could we embed an Envoy? Would we even want to
• Should we embed the uuid codebase into the monorepo?
• Should we unwind the Gradle plugin from the monorepo?
• Dependency bundling: SBOMs?
• What does Sigstore integration look like?
• Type layouts?
• Should we support capnproto in the proto layer?
• How can we dynamically load intrinsics?
• How can we, generally, transition to a modular posture? How does that change if we assume installed resources?
• Can we be API-compatible with Deno? Bun? How would we approach this?
• What about Web IDL and bikeshed-based definitions, i.e. machine-parsed specifications?
• What would it look like to pass on most of Micronaut's features via the Elide server? How would it be configured?
• What about remote dependency fetches, like Deno?
• Kotlin compiler support?
• Hot reload support? Across languages?
• We should be benchmarking key intrinsic implementations like base64, crypto, and so on
• Should we fork GraalVM and create a dedicated binary target, like Mandrel did?
• Should VM invocations be serializable? Should this be forced, or opt-in, or opt-out?
• What is the user API for configuring a VM? What is the internal API?
• Configuration file format? Purpose? Contents?
• Cloud support: Embedding cloud SDKs and awareness?
• Secret support: Long anticipated via env layer
• Could we re-use some of the Kotlin SDK's stdlib w3c layouts?

Micronaut modules we could be exporting upstream:

• micronaut-views layer based on SSR engine
• General VM execution engine

Devops and housekeeping:

• Need to write a better contributor's guide
• Need to list DCO, CLA in repository and licensing guide