flexible-vectors
mojo.js
flexible-vectors | mojo.js | |
---|---|---|
4 | 15 | |
43 | 475 | |
- | 1.3% | |
2.8 | 7.9 | |
about 1 month ago | 11 days ago | |
WebAssembly | JavaScript | |
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.
flexible-vectors
-
Mojo – a new programming language for all AI developers
Wonderful language. Only complaint (so far) : SIMD should be named Vector and dispatched to whatever SIMD/vector pipeline the host offers, similar to Flexible Vectors proposal in WASM: https://github.com/WebAssembly/flexible-vectors/blob/main/pr...
-
AVX 512 will be the future
Abstract vectorization instructions in wasm will make life a lot easier
https://github.com/WebAssembly/flexible-vectors/blob/main/pr... great proposal!
Mapping to whatever hardware is available as some sort of micro library
-
Take More Screenshots
I think SIMD was a distraction to our conversation, most code doesn't use it and in the future the length agnostic, flexible vectors; https://github.com/WebAssembly/flexible-vectors/blob/master/... are a better solution. They are a lot like RVV; https://github.com/riscv/riscv-v-spec, research around vector processing is why RISC-V exists in the first place!
I was trying to find the smallest Rust Wasm interpreters I could find, I should have read the source first, I only really use wasmtime, but this one looks very interesting, zero deps, zero unsafe.
16.5kloc of Rust https://github.com/rhysd/wain
The most complete wasm env for small devices is wasm3
20kloc of C https://github.com/wasm3/wasm3
I get what you are saying as to be so small that there isn't a place of bugs to hide.
> “There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.” CAR Hoare
Even a 100 line program can't be guaranteed to be free of bugs. These programs need embedded tests to ensure that the layer below them is functioning as intended. They cannot and should not run open loop. Speaking of 300+ reimplementations, I am sure that RISC-V has already exceeded that. The smallest readable implementation is like 200 lines of code; https://github.com/BrunoLevy/learn-fpga/blob/master/FemtoRV/...
I don't think Wasm suffers from the base extension issue you bring up. It will get larger, but 1.0 has the right algebraic properties to be useful forever. Wasm does require an environment, for archival purposes that environment should be written in Wasm, with api for instantiating more envs passed into the first env. There are two solutions to the Wasm generating and calling Wasm problem. First would be a trampoline, where one returns Wasm from the first Wasm program which is then re-instantiated by the outer env. The other would be to pass in the api to create new Wasm envs over existing memory buffers.
See, https://copy.sh/v86/
MS-DOS, NES or C64 are useful for archival purposes because they are dead, frozen in time along with a large corpus of software. But there is a ton of complexity in implementing those systems with enough fidelity to run software.
Lua, Typed Assembly; https://en.wikipedia.org/wiki/Typed_assembly_language and Sector Lisp; https://github.com/jart/sectorlisp seem to have the right minimalism and compactness for archival purposes. Maybe it is sectorlisp+rv32+wasm.
If there are directions you would like Wasm to go, I really recommend attending the Wasm CG meetings.
https://github.com/WebAssembly/meetings
When it comes to an archival system, I'd like it to be able to run anything from an era, not just specially crafted binaries. I think Wasm meets that goal.
https://gist.github.com/dabeaz/7d8838b54dba5006c58a40fc28da9...
-
Exploring SIMD performance improvements in WebAssembly
Thanks! Good points, I think in general the fixed-width "packed" SIMD ISAs have the downsides that you mentioned.
But it seems that WebAssembly doesn't have length-agnostic SIMD instructions yet. There is an open proposal to add this though: https://github.com/WebAssembly/flexible-vectors
mojo.js
-
Nue: A React/Vue/Vite/Astro Alternative
Have you looked at https://mobx-keystone.js.org/ by any chance?
I've been quite enjoying keystone + lit (or react if required) of late and at the very least it feels like solid prior art towards MVC stuff.
Also https://mojojs.org/ for server side.
(I'm not saying "use these" even if I quite enjoy using them myself, but they're my reference points for comparison here)
- Mojo – a new programming language for all AI developers
-
Does node have a Rails-like framework? (that has isn't dead)
Mojo.js
-
Choose boring tools
A final interesting note is that the Mojolicious developer has also recently(-ish) created Mojo.js, which is Mojolicious implemented in Typescript.
-
What's your go-to web framework for new web APIs?
mojo.js, it's a very old school web framework.
-
Mojo.js is a port of Perl's Mojolicious to TypeScript
Express middleware support is on the planned feature list for 2.0 and beyond. Could also be implemented as a 3rd party plugin using the existing hook API though. https://github.com/mojolicious/mojo.js/issues/66
-
Perl on Rails (2007)
Just in case you missed it, Mojolicious is also available for TypeScript now, and the developer experience is pretty close to the Perl original. ;) https://mojojs.org
-
[AskJS] Is MVC "dead"?
Aside from NestJS there is also mojo.js still innovating on the old MVC formula with TypeScript.
- Ask HN: Getting tired of complexity in web development
What are some alternatives?
wain - WebAssembly implementation from scratch in Safe Rust with zero dependencies
wshook - Easily intercept and modify WebSocket requests and message events.
rust-wasm - A simple and spec-compliant WebAssembly interpreter
jsynchronous - Jsynchronous.js - Data synchronization for games and real-time web apps.
wai - a wasm interpreter written by rust
hono - Web Framework built on Web Standards
tropy - Research photo management
nue - The Content First Web Framework
WasmCert-Isabelle - A mechanisation of Wasm in Isabelle.
primate - Polymorphic development platform
simd-wasm-profiling - Exploring SIMD performance improvements in WebAssembly
htmlparser2 - The fast & forgiving HTML and XML parser