component-model
CLI11
component-model | CLI11 | |
---|---|---|
33 | 12 | |
837 | 3,109 | |
4.3% | 1.9% | |
8.2 | 8.5 | |
7 days ago | 7 days ago | |
Python | C++ | |
GNU General Public License v3.0 or later | 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.
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
CLI11
-
C++ Game Utility Libraries: for Game Dev Rustaceans
Book: CLI11 book
-
Command line interface library
The most feature-rich C++ CLI library is CLI11. Other popular choices include Boost.ProgramOptions, argparse, cxxopts and others.
-
Create Elegant C++ Spatial Processing Pipelines in WebAssembly
CLI11 provides all the features you expect in a powerful command line parser, with a beautiful, minimal syntax and no dependencies beyond C++11. itk-wasm enhances CLI11 with a itk::wasm::Pipeline wrapper to support efficient execution in multiple Wasm contexts, scientific data structures, and lovely colorized help output 🥰.
-
CLI11 is making all the other options libraries look bad, does anyone have a comparison from experience?
Does anyone have feedback on the possible problems with CLI11 and comparisons to any other thing available in the wild not limited to the choices I tried before? Looks like a very well-thought out library according to its documentation: https://cliutils.github.io/CLI11/book/
-
Creating a CLI in C++
I'd recommend to use CLI11. I was baffled by how much it can do.
-
3 Ways To Parse Command Line Arguments in C++: Quick, Do-It-Yourself, Or Comprehensive
I use https://github.com/jarro2783/cxxopts.git or https://github.com/CLIUtils/CLI11, or if boost is involved anyway, boost.program_options.
-
Carregando dependências em projetos C++ usando o CMake
get_dependency(spdlog "https://github.com/gabime/spdlog" v1.8.5) get_dependency(CLI11 "https://github.com/CLIUtils/CLI11" v1.9.1) get_dependency(GoogleTest "https://github.com/google/googletest" master)
-
cmdlime - possibly the least verbose command line parsing library for C++17
Maybe https://github.com/CLIUtils/CLI11? I really like this one and it looks like it supports TOML
-
Why no standard library support for command line parsing?
I found https://github.com/jarro2783/cxxopts to be useful and https://github.com/CLIUtils/CLI11 to be really helpful if you need an non-trivial interface.
What are some alternatives?
wit-bindgen - A language binding generator for WebAssembly interface types
jarro2783/cxxopts - Lightweight C++ command line option parser
bartholomew - The Micro-CMS for WebAssembly and Spin
clipp - easy to use, powerful & expressive command line argument parsing for modern C++ / single header / usage & doc generation
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
gflags - The gflags package contains a C++ library that implements commandline flags processing. It includes built-in support for standard types such as string and the ability to define flags in the source file in which they are used. Online documentation available at:
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
args - A simple header-only C++ argument parser library. Supposed to be flexible and powerful, and attempts to be compatible with the functionality of the Python standard argparse library (though not necessarily the API).
spec - WebAssembly specification, reference interpreter, and test suite.
Boost.Program_options - Boost.org program_options module
proposals - Tracking WebAssembly proposals
Vcpkg - C++ Library Manager for Windows, Linux, and MacOS