luajit
wasmer-python
luajit | wasmer-python | |
---|---|---|
1 | 13 | |
540 | 1,958 | |
- | 0.8% | |
10.0 | 6.1 | |
over 4 years ago | 8 months ago | |
C | Rust | |
GNU General Public License v3.0 or later | MIT License |
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.
luajit
-
Back-end languages are coming to the front-end
> No offence, but have you written any compilers or interpreters?
I have, but nothing sophisticated.
> The points that you discuss [...] may be performance concerns for application developers [...] but they have very little to do with the optimisations you can make as a compiler/interpreter writer. [...] The only one that's somewhat relevant is 'global scope by default'
I didn't mean to imply that these where the three common traits that make both Javascript and Lua particularly hard to optimize, I just picked them as examples for how Javascript and Lua are closer to each other than most other dynamic languages.
But let's dig in a bit on your claim that things like all numbers being doubles or having a array cum map cum record type has very little to do with the optimizations you can make as a compiler/interpreter writer, because it sure seems to me that LuaJIT and V8 do a bunch of optimizations around these things. Both have dual number representations under the hood and will try to avoid representing numbers that remain in the domain of 32 bit integers as double values internally when that gives performance gains. The logic for figuring out if that's the case doesn't seem to be super-straightforward or target architecture independent from looking at the comments in <https://github.com/LuaDist/luajit/blob/master/src/lj_opt_nar...>.
LuaJIT furthermore uses NaN tagging (as do some JS engines, although not V8), which looks less attractive to me as a representation strategy if your numbers are not all/mostly notional doubles (as is indeed the case in newer version of Lua where 64bit integers are the dominant number type)
Also, as far as the super-flexible lua tables are concerned, I'm pretty sure LuaJIT goes through some amount of trouble to specialize various common use cases of tables, e.g. as arrays without holes, and surprise, so does V8 (https://v8.dev/blog/fast-properties#elements-or-array-indexe...). I don't think you'd find something equivalent in a high performance scheme implementation.
> but this doesn't touch the surface of the issues that make JS hard to optimise, such as the fact that your, say, memoisation of an object property or method may be broken by an `eval` call of an arbitrary runtime value somewhere else in the code (which, due to asynchronicity, could take place at more or less any time from the point of view of your given 'peephole').
Eval belongs to a core set of features that basically all popular dynamic languages share that presents headaches for high performance implementations. How is Javascript's eval particularly problematic in this regard, and specifically much more so than Lua's loadstring/load?
More generally what do you think makes (pre-ES6) javascript significantly harder to optimize than lua 5.0?
wasmer-python
-
WebAssembly: byte-code of the future
It's also possible to do this from many other languages. For example rust, ruby, python or from the CLI.
-
WebAssembly: Adding Python Support to WASM Language Runtimes
PyOdide isn't currently supported outside of browsers, though that might change.
Either way, I couldn't figure out how to do the above sequence of steps with any of the available Python WASM runtimes - they're all very under-documented at the moment, sadly. I tried all three of these:
- https://github.com/wasmerio/wasmer-python
- https://github.com/bytecodealliance/wasmtime-py
- https://github.com/wasm3/pywasm3
- Back-end languages are coming to the front-end
-
Running python in a browser (no sever)
Well... not with that attitude.
-
WAGI: WebAssembly Gateway Interface
Not just for web either: if you ship WebAssembly bytecode as part of your python package, you can push your platform dependencies out to a wasm runtime and skip most of the build matrix.
A runtime like wasmer-python [0] is only 1.5MB.
[0]: https://github.com/wasmerio/wasmer-python
- Wasmer Python
- Lona - A web framework for responsive web apps in full python
- What do you guys think of Dominate? Use cases?
- Can you convert python to JavaScript with libraries?
What are some alternatives?
diode - Scala library for managing immutable application model
streamlit - Streamlit — A faster way to build and share data apps.
htmx - </> htmx - high power tools for HTML
reactpy - It's React, but in Python
mumba - Write web-native p2p distributed apps in Swift (and others)
wagi - Write HTTP handlers in WebAssembly with a minimal amount of work
reactor - Phoenix LiveView but for Django
aiohttp-json-rpc - Implements JSON-RPC 2.0 using aiohttp
django-unicorn - The magical reactive component framework for Django ✨
wasi-experimental-http - Experimental outbound HTTP support for WebAssembly and WASI
Scala.js - Scala.js, the Scala to JavaScript compiler
dominate - Dominate is a Python library for creating and manipulating HTML documents using an elegant DOM API. It allows you to write HTML pages in pure Python very concisely, which eliminate the need to learn another template language, and to take advantage of the more powerful features of Python.