hashlink
component-model
hashlink | component-model | |
---|---|---|
5 | 33 | |
791 | 828 | |
1.3% | 3.3% | |
8.8 | 8.2 | |
10 days ago | 7 days ago | |
C | Python | |
MIT License | GNU General Public License v3.0 or later |
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.
hashlink
-
3D and 2D: Testing out my cross-platform graphics engine
> The point of Haxe seems to be as a meta-compiler to generate code for a bunch of different languages/compilers?
That's basically correct, although there is also a cross platform runtime called Hashlink but is unsupported by Kha.
https://hashlink.haxe.org/
-
Ask HN: Does anyone here use Haxe?
The person who made Haxe (Nicolas Canesse) went on to found Shiro Games (https://shirogames.com), a game development company. I believe all their games are made in Haxe. The latest one, "Dune: Spice Wars" was released this September and Google says the engine is HashLink (https://hashlink.haxe.org/) which is a VM for Haxe.
I don't know any other companies who are releasing games in Haxe today.
-
SDL2 is zlib licensed but why it's not included in other code repositories?
I've seen it in SDL2_image source and also Hashlink repository. They included other dependencies but removed SDL2 in their source code (gitignored it).
-
Try the new try.haxe!
Well, it also has its very own [Hashlink, virtual machine](https://hashlink.haxe.org/).
And it can also compile down to various bytecodes (like JVM), not just to other languages.
-
lots of errors when trying to compile cpp chat server file
According to this, I think you have to specify -lwsock32 -lws2_32 to use the built-in .lib files that contain __imp_recv etc.
component-model
-
Tree-shaking, the horticulturally misguided algorithm
I don't think that's a very good goal. Jettisoning the DOM means jettisoning accessibility and being able to leverage everything that the browser gives you out-of-the-box. You have to render to a canvas and build everything from scratch. I think Wasm is great for supplementing a JS app, not replacing it (e.g. using a Wasm module to do some calculations in a Worker). I like to use the right tool for the job, and trying to use something other than JS to build a web app just seems a little janky to me.
At one point, there was a Host Bindings proposal that would enable you to do DOM manipulation (it looks like it was archived and moved to the Component Model spec [1]). That would probably be the ideal way to avoid as much JS as possible. However, browser vendors have been heavily optimizing their JS runtimes, and in some cases, Wasm may actually be slower than JS.
I've been following Wasm's progress for several years, which has been slow, but steady. Ironically, I think the web is actually the worst place to use it. There's so much cool non-web stuff being done with it and I'm more interested to see where that goes.
[1] https://github.com/WebAssembly/component-model?tab=readme-ov...
-
3D and 2D: Testing out my cross-platform graphics engine
Well the great thing about WebAssembly is that you can port QT or anything else to be at a layer below -- thanks to WebAssembly Interface Types[0] and the Component Model specification that works underneath that.
To over-simplify, the Component Model manages language interop, and WIT constrains the boundaries with interfaces.
IMO the problem here is defining a 90% solution for most window, tab, button, etc management, then building embeddings in QT, Flutter/Skia, and other lower level engines. Getting a good cross-platform way of doing data passing, triggering re-renders, serializing window state is probably the meat of the interesting work.
On top of that, you really need great UX. This is normally where projects fall short -- why should I use this solution instead of something like Tauri[2] which is excellent or Electron?
[0]: https://github.com/WebAssembly/component-model/blob/main/des...
[1]: https://github.com/WebAssembly/component-model/blob/main/des...
[2]: https://tauri.app/
-
Missing the Point of WebAssembly
While I don't necessarily agree with the unnecessary, unsupported casual, & cheap contempt culture here ("unshackle the web from the mess that is JavaScript", "places that don't really need these problems to be solved")...
WebAssembly component-model is being developed to allow referring to and passing complex objects between different modules and the outside world, by establishing WebAssembly Interface Types (WIT). It's basically a ABI layer for wasm. This is a pre-requisite for host-object bridging, bringing in things like DOM elements.
Long running effort, but it's hard work and there's just not that many hands available for this deep work. Some assorted links with more: https://github.com/WebAssembly/component-model https://www.fermyon.com/blog/webassembly-component-model https://thenewstack.io/can-webassembly-get-its-act-together-...
It's just hard work, it's happening. And I think the advantages Andy talks to here illuminate very real reasons why this tech can be useful broadly. The ability to have plugins to a system that can be safely sandboxed is a huge win. That it's in any language allows much wider ecosystem of interests to participate, versus everyone interested in extending your work also having to be a java or c++ or rust developer.
-
Steel – An embedded scheme interpreter in Rust
A. Sure, but it isn't sufficiently beneficial for the cost.
B. WebAssembly is immature for developing a plugin system because of the lack of a sufficient ABI: https://github.com/WebAssembly/component-model
C. There aren't any other languages that meet the criteria. Lua was a no-go from the start. The maintainers did not like the language, and it necessitated adding more C code to Helix which could complicate building even further. https://github.com/helix-editor/helix/discussions/3806#discu...
-
Bring garbage collected programming languages efficiently to WebAssembly
AFAIK GC is irrelevant for "direct DOM access", you would rather want to hop into the following rabbit hole:
- reference types: https://github.com/WebAssembly/reference-types/blob/master/p...
- interface types (inactive): https://github.com/WebAssembly/interface-types/blob/main/pro...
- component model: https://github.com/WebAssembly/component-model
If this looks like a mess, that's because it is. Compared to that, the current solution to go through a Javascript shim doesn't look too bad IMHO.
-
Rust Is Surging Ahead in WebAssembly (For Now)
The wasm idl (called WIT) is actively being worked on here: https://github.com/WebAssembly/component-model/blob/main/des...
Being able to access DOM is definitely an objective. It's just taking a lot longer than folks guessed to build a modular wasm ABI.
-
Reaching the Unix Philosophy's Logical Extreme with WebAssembly
The WASM Component Model
https://github.com/WebAssembly/component-model
- WASI: WebAssembly System Interface
-
Introducing - Wasmer Runtime 4.0
Take a look at the python abi to see what the structure looks like for calling into components https://github.com/WebAssembly/component-model/tree/main/design/mvp/canonical-abi
- How WebAssembly Is Eating the Database
What are some alternatives?
SDL - Simple Directmedia Layer
wit-bindgen - A language binding generator for WebAssembly interface types
awesome-haxe-gamedev - Resources for game development on haxe
bartholomew - The Micro-CMS for WebAssembly and Spin
copybara - Copybara: A tool for transforming and moving code between repositories.
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
awesome-config - Configuration and widgets for Awesome WM in Lua and MoonScript
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
reaper-with-typescript-starter
spec - WebAssembly specification, reference interpreter, and test suite.
haxe.io - The home of the Haxe Roundup's (Work in Progress)
proposals - Tracking WebAssembly proposals