Som
watt
Som | watt | |
---|---|---|
8 | 21 | |
22 | 1,222 | |
- | - | |
0.0 | 7.3 | |
over 1 year ago | 18 days ago | |
C++ | Rust | |
GNU General Public License v3.0 only | 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.
Som
-
Making Smalltalk on a Raspberry Pi (2020)
> Smalltalkish
Have a look at the SOM dialect which is successfully used in education: http://som-st.github.io/
Here is an implementation in C++ which runs on LuaJIT: https://github.com/rochus-keller/Som/
> unfortunately out of print book Smalltalk 80: the language and its implementation is commonly recommended
I assume you know this link: http://stephane.ducasse.free.fr/FreeBooks/BlueBook/Bluebook....
Here is an implementation in C++ and Lua: https://github.com/rochus-keller/Smalltalk
- Do transpilers just use a lot of string manipulation and concatenation to output the target language?
-
Ask HN: Admittedly Useless Side Projects?
- https://github.com/rochus-keller/Smalltalk/ Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file
- https://github.com/rochus-keller/Som/ Parser, code model, navigable browser and VM for the SOM Smalltalk dialect
- https://github.com/rochus-keller/Simula A Simula 67 parser written in C++ and Qt
> do you regret those endeavours?
No, not in any way; the projects were very entertaining and gave me interesting insights.
-
Ask HN: Recommendation for general purpose JIT compiler
If your DSL is statically typed then I recommend that you have a look at the Mono CLR; it's compatible with the ECMA-335 standard and the IR (CIL) is well documented, even with secondary literature.
If your DSL is dynamically typed I recommend LuaJIT; the bytecode is lean and documented (not as good as CIL though). LuaJIT also works well with statically typed languages, but Mono is faster in the latter case. Even if it was originally built for Lua any compiler can generate LuaJIT bytecode.
Both approaches are lean (Mono about 8 MB, LuaJIT about 1 MB), general purpose, available on many platforms and work well (see e.g. https://github.com/rochus-keller/Oberon/ and https://github.com/rochus-keller/Som/).
-
When is Smalltalk's speed an issue?
At the latest when you run a benchmark suite like Are-we-fast-yet; here are some measurment results: http://software.rochus-keller.info/are-we-fast-yet_crystal_lua_node_som_pharo_i386_results_2020-12-29.pdf. See also https://github.com/rochus-keller/Som/ and https://github.com/rochus-keller/Smalltalk.
-
LuaJIT for backend?
LuaJIT is well suited as a backend/runtime environment for custom languages; I did it several times (see e.g. https://github.com/rochus-keller/Smalltalk, https://github.com/rochus-keller/Som/, https://github.com/rochus-keller/Oberon/). I also implemented a bit of infrastructure to ease the reuse: https://github.com/rochus-keller/LjTools. LuaJIT has some limitations though; if you require closures you have to know that the corresponding LuaJIT FNEW bytecode is not yet supported by the JIT, i.e. switches to the interpreter; as a work-around I implemented my own closures; LuaJIT also doesn't support multi-threading, but co-routines; and there is no debugger, and the infrastructure to implement one has limitations (i.e. performance is low when running to breakpoints). For most of my projects this was no issue. Recently I switched to CIL/Mono for my Oberon+ implementation which was a good move. But still I consider LuaJIT a good choice if you can cope with the mentioned limitations. The major advantage of LuaJIT is the small footprint and impressive performance for dynamic languages.
-
Optimizing an old interpreted language: where to begin?
One option is to leverage someone else's JIT: you could, for example, rewrite the interpreter to transpile to Lua source, which is then run in LuaJIT. There's a Smalltalk dialect which does this successfully; the Lua version runs in 1/12th the time of the C interpreted version. https://github.com/rochus-keller/Som You can use LuaJIT's FFI to call back into the Stunt server, or else just rewrite it completely in Lua --- large parts of the Stunt server will just go away in a native Lua implementation (e.g. the object database is just a table). Javascript would be another candidate for this.
-
JITted lang which is faster than C?
This is a completely different kind of measurement; unfortunately this is not clear enough from my Readme. I wanted to find out, how well my naive Bluebook interpreter performs on LuaJIT (using my virtual meta tracing approach) compared to Cog, which is a dedicatd Smalltalk VM optimized with whatever genious approaches over two decades (or even longer considering the long experience record by Elliot). This experiment continues in https://github.com/rochus-keller/Som, because I didn't want to modify the original Smalltalk image. I found that my naive LuaJIT based approach is about factor seven behind the highly optimized Cog/Spur, and further improvements would require similar optimization tricks as in the latter.
watt
-
Rust devs push back as Serde project ships precompiled binaries
The precompiled binary is not a sandboxed WASM binary. Despite the name "watt" it has nothing to do with https://github.com/dtolnay/watt . You can look at the actual code to see for yourself.
- Arbitrary code execution during compilation – rust
-
syn v2.0.0 released
* Related: watt is one approach to pre-compile proc-macro crates using WASM.
-
My first year with Rust: The good, the bad, the ugly
In addition to thiserror and anyhow, our resident superhuman Rust-improving Robot, dtolnay, also developed an experiment in distributing precompiled proc macros as WebAssembly named Watt and, though I never bothered to create a Zulip account so I don't know what was said, I'm told there has been discussion around the idea of implementing something in that vein.
-
Rust is coming to the Linux kernel
I think when we have Cranelift, Mold, and maybe Watt all working together then compile times will basically be a non-issue. It'll be a few years though.
- watt: Runtime for executing (Rust) procedural macros as WebAssembly
-
Security advisory: malicious crate rustdecimal | Rust Blog
Check out https://github.com/dtolnay/watt - it's a really interesting solution to the problem!
-
Backdooring Rust crates for fun and profit
I really like the idea of Watt: https://github.com/dtolnay/watt Run macros in a wasm sandbox so they can't touch anything you don't explicitly allow.
-
NPM malware and what it could imply for Cargo
I really wish there was more interest in getting something like Watt upstreamed.
- Things I hate about Rust, redux
What are some alternatives?
Smalltalk - Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file
godot-wasm-engine
rockstar - Makes you a Rockstar C++ Programmer in 2 minutes
cargo2nix - Granular builds of Rust projects for Nix
qbe-rs - QBE IR in natural Rust data structures
cap-std - Capability-oriented version of the Rust standard library
ubpf - Userspace eBPF VM
kani - Kani Rust Verifier
sljit - Platform independent low-level JIT compiler
cargo-deny - ❌ Cargo plugin for linting your dependencies 🦀
Oberon - Oberon parser, code model & browser, compiler and IDE with debugger
awesome-wasm-runtimes - A list of webassemby runtimes