iconvg
spec
Our great sponsors
iconvg | spec | |
---|---|---|
6 | 12 | |
660 | 3,061 | |
0.8% | 0.8% | |
3.3 | 8.3 | |
6 months ago | 1 day ago | |
C | WebAssembly | |
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.
iconvg
-
A challenger to the throne of vector graphics. SVG is dead, long live TinyVG!
The HN thread also mentions Lottie from AirBnB and IconVG from Not-an-official-Google-product.
-
A challenger to the throne of vector graphics. SVG is dead, long live TinyVG
IconVG author here. Happy to discuss.
Animation is issue #2 on https://github.com/google/iconvg and I have some ideas but no code yet. I'm also midway through changing the current "version 0" format into a "version 1" format, dropping things like the ArcTo op (inspired by SVG) precisely with one eye on (future) animation support. The ArcTo large-arc-flag, like any boolean-typed value, is impossible to interpolate smoothly.
-
IconVG is a compact, binary format for simple vector graphics
https://github.com/google/iconvg/blob/main/spec/iconvg-spec.... also doesn't explain what relative cubeTo does, though from the context (2D vector graphics), “relative” must mean the co-ordinates are relative to the position of the cursor (as opposed to “absolute” which is relative to some fixed origin), and “cube” probably refers to cubic interpolation.
spec
-
WASM Instructions
You can parse many things from this file, what are you trying to extract?
https://github.com/WebAssembly/spec/blob/main/document/core/...
-
The fastest word counter in JavaScript
Still strikes me as super sad JS never got SIMD support. It seemed like there were some strong candidate specs. On Node there are some add-on npm libraries that implement.
My understanding was the main protest was that we would get wasm & some certain implementers said they wanted to focus their energy on wasm.
That was well over half a decade ago & wasm is still in incredible infancy, with basically only statically linked capabilities in the spec.
Wasm SIMD proposal itself only merged into wasm in November 2021. https://github.com/WebAssembly/spec/pull/1391
It seems really unfortunate to have decided to keep JS the slow inferior language.
-
Is Blazor server and Blazor Webassembly going to be a big market? I am trying to figure out a niche to go with and I have some asp.net core mvc experience but I am working on a e-commerce .net6 Blazor Webassembly app.
Blazor and WASM itself (outside of dotnet) are relatively new tools and they already show impressive results. They will keep getting better with every release. E.g. this proposal https://github.com/WebAssembly/spec/blob/main/proposals/simd/SIMD.md which should bring WASM closer to "near native speed". Blazor already started working on it true.
-
Smolnes: A NES Emulator In
Big fan of this author's work.
They have a Gameboy emulator written in C, which can be compiled to WASM and run in the browser.
https://github.com/binji/binjgb
I learned a lot from the code.
Also I love this project with a bunch of demos in hand-written WebAssembly Text (WAT) format, which is like low-level Lisp that works only with raw memory, numbers, and minimal syntax.
https://github.com/binji/raw-wasm
Then I discovered the same author is quite active in the WebAssembly ecosystem, including specs and tooling. Fascinating stuff!
https://github.com/WebAssembly/spec
https://github.com/WebAssembly/wabt
-
Exploring WebAssembly, The Underlying Technology Behind Blazor WASM.
[The WebAssembly specification (https://webassembly.github.io/spec/) maintains that the standards apply to more than just the browser host, but also to any other compliant host runtime (what the specification refers to as an embedder).
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
Heya,
(1) Thank you for implementing this in JSC!! I hope they take it, it makes it into Safari, and the tail-call proposal advances.
(2) I don't think you are exactly right about the call stack being observable via thrown exceptions. There's no formal spec for the v3 exceptions proposal yet, but in the documents and tests, there's nothing that would change in WebAssembly core to make the call stack observable. It's true that the proposal amends the JS API (but only the JS API) to describe a traceStack=true option; from Wasm's perspective I understand that's just an ordinary exception that happens to include an externref value (just like any other value) to which Wasm itself attaches no special significance. The engine can attach a stack trace if it wants, but there's no requirement (here) about what that stack trace contains or whether some frames might have been optimized out.
(3) I think the real reason that a Wasm engine can't implicitly make tail calls proper is that the spec tests forbid it, basically because they didn't want the implementation base to split by having some engines perform an optimization that changes the space complexity of a program, which some programs would have started to depend on (the spec tests say: "Implementations are required to have every call consume some abstract resource towards exhausting some abstract finite limit, such that infinitely recursive test cases reliably trap in finite time. This is because otherwise applications could come to depend on it on those implementations and be incompatible with implementations that don't do it (or don't do it under the same circumstances.)" More discussion here: https://github.com/WebAssembly/spec/issues/150
- WebAssembly 2.0 Working Draft
- A challenger to the throne of vector graphics. SVG is dead, long live TinyVG
-
Microsoft joins Bytecode Alliance to advance WebAssembly – aka the thing that lets you run compiled C/C++/Rust code in browsers
The WASM paper discusses that in the final section: https://github.com/WebAssembly/spec/blob/master/papers/pldi2017.pdf
-
Is there a small, well-specified language with lots of example programs?
WebAssembly has a formal specification that includes both operational semantics and natural language-based descriptions of everything in the language. The official repository also has a lot of tests. Besides tests, you should be able to find lots of examples by searching.
What are some alternatives?
svgomg - Web GUI for SVGO
uwm-masters-thesis - My thesis for my Master's in Computer Science degree from the University of Wisconsin - Milwaukee.
Method-Draw - Method Draw, the SVG Editor for Method of Action
Oberon - Oberon parser, code model & browser, compiler and IDE with debugger
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond
meetings - WebAssembly meetings (VC or in-person), agendas, and notes
specification - The specification for TinyVG. This is the central authority for the file system
component-model - Repository for design and specification of the Component Model
resvg - An SVG rendering library.
proposals - Tracking WebAssembly proposals
Smiley Rating - SmileyRating is a simple rating bar for android. It displays animated smileys as rating icon.
wit-bindgen - A language binding generator for WebAssembly interface types