pyscript
wizer
pyscript | wizer | |
---|---|---|
42 | 10 | |
17,452 | 879 | |
0.3% | 1.6% | |
9.2 | 7.1 | |
3 days ago | 21 days ago | |
Python | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pyscript
- Show HN: Dillo 3.1.0 released after 9 years
-
RustPython
You are right for the most part. I attended a talk about pyscript[1] (runs python in the browser using wasm which is similar) and there is a 2x performance hit.
[1] https://pyscript.net
-
Python HTTP library 'urllib3' now works in the browser
PyScript maintainer here - I'd love to hear more about this application! Either here, or over on our Discord (invite link is on the GitHub Page [1]).
[1] https://github.com/pyscript/pyscript?tab=readme-ov-file#summ...
-
Convert code from alpha version to latest version. Where to find complete and precise changelogs?
For the first question - why your code previously created an HTML node but now just prints out the literal characters of the HTML - that was a change made in 2022.12.1, in Pull Request 915 to be specific. You can check out the single-line change that caused this, if you want. Essentially, calls to Element.write() or display() have their contents escaped by default, which wasn't the case before.
-
How to access py-click from py-script?
Note that in the current release (2023.03.1 at time of writing), py-[event] listeners are only hooked up once at page-load time, so changing that attribute after the page loads won't do anything. In the upcoming release, py-[event] handlers are dynamically attached and managed each time a py-[event] attribute on the page is changed. (PR 1435)
-
After tearing my hair out writing JavaScript the last few days how close are we to Python in the browser?
PyScript started as a usability layer around Pyodide for those not used to working in JS. It's now working on things like incorporating the Micropython runtime as an alternative, moving the interpreter to a worker thread, adding a plugins ecosystem, easier events API's, and more.
-
Any way to display "working..." while waiting for py-reml to evaluate?
Some answers: https://github.com/pyscript/pyscript/discussions/1414
-
How does PyScript work with 3rd party JS libraries, like Three.js ?
You can also check out the WebGL demo from the PyScript examples, which uses Thee.JS.
-
NameError question
Mainly, the pys-onClick syntax that was present in earlier version in favor of the new py-* syntax, where * is a browser event name. It also takes a string of executable python instead of the name of a Callable. So in your case, you'd use py-click="get_input()". (There's a long-in-progress PR on GitHub with more examples.)
- Intrebare frontend
wizer
-
RustPython
> once by the wasm runtime to compile the rust-python wasm
I'm not sure what you mean by that. The runtime doesn't compile WASM, it simply executes it.
There are tools for dealing with interpreter runtime overhead this by pre-initalizing the environment like Wizer[0]. ComponentizeJS[1] uses it to pre-initialize the Spidermoney engine it packages to gain fast startup times (and you can then prune the initialization only code with wasm-opt). As techniques like ComponentizeJS are also being applied for a specific set of interpreted files, you can even prune parts of the interpreter that would never be used for that specific program. If you want to go even further you could record specific execution profiles and optimize further by those.
[0]: https://github.com/bytecodealliance/wizer
[1]: https://github.com/bytecodealliance/ComponentizeJS
- Are V8 isolates the future of computing?
-
Netlify Edge Functions: A new serverless runtime powered by Deno
Edge functions are typically run intermittently, with their runtime stopped to free up resources between runs. Therefore a big factor is startup and shutdown speed. Containers are pretty bad there. Deno is better, and WASM is unbeatable, especially with things like Wizer[0].
[0]https://github.com/bytecodealliance/wizer
-
Building a WebAssembly-powered serverless platform
I imagine startup cost could be amortized by something like wizer: https://github.com/bytecodealliance/wizer
-
Containerless! How to Run WebAssembly Workloads on Kubernetes with Rust
There are security benefits to running each request in its own instance, as it helps prevent accidental leaking of state between requests. To avoid doing lots of expensive initializations, we have a tool called wizer which lets users run their program's initialization once, create a snapshot, and then use that snapshot to do fast startups that don't rerun the whole initialization each time.
-
Is it possible in Rust to save the complete state of a program and restore it later? Such as may be accomplished in some implementations of Common Lisp
See https://github.com/bytecodealliance/wizer for an implementation of this approach.
-
Bytecode Alliance
It should probably be named "Making JavaScript to startup fast on WebAssembly", since the runtime speed is not really improved by the approach they exposed.
Besides that I think Wizer [1] is both an elegant and a simple solution to speed up startup speed with Wasm.
[1] - https://github.com/bytecodealliance/wizer#using-wizer-as-a-l...
-
A JavaScript optimizing compiler
A similar project, for WebAssembly so with limited scope is this: https://github.com/bytecodealliance/wizer. And somehow similar but limited on LLVM IR a colleague worked on this for Cheerp (the compiler used here as backend): https://github.com/leaningtech/cheerp-meta/wiki/Cheerp-PreExecuter.
- Wizer: snapshot an initialized Wasm instance and save the result as a new, pre-initialized Wasm module. Up to 6x faster start up on my test workloads
- Wiser: snapshot an initialized Wasm instance and save the result as a new, pre-initialized Wasm module. Up to 6x faster start up on my test workloads
What are some alternatives?
brython - Brython (Browser Python) is an implementation of Python 3 running in the browser
quickjs-emscripten - Safely execute untrusted Javascript in your Javascript, and execute synchronous code that uses async functions
appdaemon - :page_facing_up: Python Apps for Home Automation
TablaM - The practical relational programing language for data-oriented applications
pyodide - Pyodide is a Python distribution for the browser and Node.js based on WebAssembly
wasmtime - A fast and secure runtime for WebAssembly
django-readers - A lightweight function-oriented toolkit for better organisation of business logic and efficient selection and projection of data in Django projects.
go - The Go programming language
Home Assistant - :house_with_garden: Open source home automation that puts local control and privacy first.
go-wasm-bake - Experimenting with eager evaluation of Go WASM code
wasm3 - 🚀 A fast WebAssembly interpreter and the most universal WASM runtime
wagi - Write HTTP handlers in WebAssembly with a minimal amount of work