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

LLRT Roadmap & Priorities #635

Open
richarddavison opened this issue Oct 18, 2024 · 8 comments
Open

LLRT Roadmap & Priorities #635

richarddavison opened this issue Oct 18, 2024 · 8 comments

Comments

@richarddavison
Copy link
Contributor

richarddavison commented Oct 18, 2024

Below is a high level list of LLRTs priorities and roadmap items. Note that these are not final and are subject to change.

2024

  • Increased WinterCG compliance
  • SubtleCrypto SubtleCrypto #184
  • Switch to more activity maintained QuickJS - Next Generation fork
  • Better documentation (website, examples, do's and dont's etc)
  • Partially native web streams
  • Increased release cadence

2025

  • HTTP & HTTPs module
  • PGO + PLO + Bolt/Propeller optimized binaries
  • 1.0 release
  • TLS sockets/connections
  • WebSockets
  • Native Streams
  • Better unhandled promise rejection tracking
  • Better local development experience
  • Debugger
@richarddavison richarddavison pinned this issue Oct 18, 2024
@o-alexandrov
Copy link

o-alexandrov commented Oct 21, 2024

If reasonable, please consider to add a note on the expected AWS-managed LLRT runtime for Lambda service.
It should slightly improve cold starts due to the runtime caching, making LLRT even more appealing to use

@ahaoboy
Copy link
Contributor

ahaoboy commented Oct 21, 2024

Have you considered adding stdin for reading user input?

@ahaoboy
Copy link
Contributor

ahaoboy commented Oct 21, 2024

quickjs-ng/quickjs#374

The ideal situation is that the upstream qjs-ng and qjs will be merged, but it seems that this is not going well.

@richarddd
Copy link

quickjs-ng/quickjs#374

The ideal situation is that the upstream qjs-ng and qjs will be merged, but it seems that this is not going well.

We'll soon move to qjs-ng. We're waiting for DelSkayn/rquickjs#369 and DelSkayn/rquickjs#373 to be finalized. This is not to far away.

@codingnuclei
Copy link

Very exciting 🎉

Would Partially native web streams look to cover this: #318

or would that be more inline with 2025 Native Streams

@richarddd
Copy link

Very exciting 🎉

Would Partially native web streams look to cover this: #318

or would that be more inline with 2025 Native Streams

Likely the latter. We’d rather ship a more complete steams API than cut corners. But depending on how fast we can progress with the more feature complete stream API we can also do a lighter version similar to the spawn streams.

@cjnoname
Copy link

The roadmap sounds promising! I'm just wondering, if v1 is released, would LLTR become one of the default runtimes on AWS Lambda?

@ahaoboy
Copy link
Contributor

ahaoboy commented Nov 15, 2024

Will there be a way to read user input?

#175

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

No branches or pull requests

6 participants