posit-dev / posit-dev/shinylive
Long loading times with the shinylive examples - maybe room for tree-shaking or lightweight r engines?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 251
- Forks
- 25
- Avg merge
- 19m
- Merged PRs (30d)
- 2
Description
Hello,
First of all, I love what you're doing!
However, I noticed that in general, the loading times of the web app are a bit long, and I wonder if it's because the "bloatware" associated with R or Python.
Are you guys trying to implement any tree-shaking method, like the ones commonly used in web-apps, to remove all non-used code and leave a lightweight engine? I am aware that for that you need a dependency tree, but I think recently, the positron team achieved something similar? Not 100% sure.
Or alternatively, do you have a lightweight R engine implementation?
Thank you again!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating how the Shinylive browser app loads its R and Python engines, then measure the loading cost and review existing tree-shaking or lightweight-runtime work; done would require an agreed approach and evidence of reduced loading times.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r, wasm
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100