-
Notifications
You must be signed in to change notification settings - Fork 359
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
Comments
If reasonable, please consider to add a note on the expected AWS-managed LLRT runtime for Lambda service. |
Have you considered adding stdin for reading user input? |
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. |
Very exciting 🎉 Would or would that be more inline with 2025 |
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. |
The roadmap sounds promising! I'm just wondering, if v1 is released, would LLTR become one of the default runtimes on AWS Lambda? |
Will there be a way to read user input? |
Below is a high level list of LLRTs priorities and roadmap items. Note that these are not final and are subject to change.
2024
2025
The text was updated successfully, but these errors were encountered: