ITK
component-model
Our great sponsors
ITK | component-model | |
---|---|---|
7 | 33 | |
1,337 | 827 | |
1.6% | 6.5% | |
9.8 | 8.2 | |
6 days ago | 4 days ago | |
C++ | Python | |
Apache License 2.0 | 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.
ITK
-
Create Elegant C++ Spatial Processing Pipelines in WebAssembly
The itkImage.h header is ITK's standard n-dimensional image data structure.
-
Welcome and guide first-time contributors with a GitHub Action
In this post, we review how the Insight Toolkit (ITK) leverages the first-interaction GitHub Action to communicate our appreciation of the efforts of first-time contributors, establish norms for behavior, and provide civil pointers on where to find more information.
-
How to raise the quality of scientific Jupyter notebooks
Jupyter has emerged as a fundamental component in artificial intelligence (AI) solution development and scientific inquiry. Jupyter notebooks are prevelant in modern education, commercial applications, and academic research. The Insight Toolkit (ITK) is an open source, cross-platform toolkit for N-dimensional processing, segmentation, and registration used to obtain quantitative insights from medical, biomicroscopy, material science, and geoscience images. The ITK community highly values scientific reproducibility and software sustainability. As a result, advanced computational methods in the toolkit have a dramatically larger impact because they can be reproducibly applied in derived research or commercial applications.
-
Holy shit, it really seems to be working!
It also depends heavily on the toolchain. One of the first successful toolkits used to circumvent image-based security measures was ITK, originally a toolkit for medical image processing. That's not even using AI (at least back then). Here you build "piplines" by lego'ing together functions like building blocks, there are rules to it, but the sleek interface design make it very versatile. It was a nightmare to devise ways to counteract, since the crucial processing steps could easily be switched around as long as the linear algebra made sense. And when you have a toolchain excelling in fourier-space based analysis and interaction, the linear algebra makes sense in a lot of different orders of doing steps.
-
Ask HN: What is a cool technology to learn?
Yeah, Prolog is pretty cool!
Another technology I found interesting too learn is ITK (https://itk.org/). You need a different mindset using ITK than other image processing libraries.
Lisp is cool as well.
And fully homomorphic encryption.
-
Give me a starting nudge: microscopy image processing in python
VTK is a powerful visualization package, but it's more for working with 3D FEM/CFD data. There are lots of things in there though, so it may be useful. The sister project Paraview is an application which can be used to work with data interactively. Both have great Python support. There is also ITK which is focused on with image data, like medical scans - never used it, though.
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?
OpenCV - Open Source Computer Vision Library
wit-bindgen - A language binding generator for WebAssembly interface types
VTK - Mirror of Visualization Toolkit repository
bartholomew - The Micro-CMS for WebAssembly and Spin
GDCM - Grassroots DICOM read-only mirror. Only for Pull Request. Please report bug at http://sf.net/p/gdcm
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
tesseract-ocr - Tesseract Open Source OCR Engine (main repository)
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
CImg - The CImg Library is a small and open-source C++ toolkit for image processing
spec - WebAssembly specification, reference interpreter, and test suite.
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond
proposals - Tracking WebAssembly proposals