flexible-vectors
flameshot
flexible-vectors | flameshot | |
---|---|---|
4 | 233 | |
43 | 23,309 | |
- | 1.4% | |
2.8 | 7.8 | |
about 1 month ago | 5 days ago | |
WebAssembly | C++ | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
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
flameshot
-
Show HN: I built a free in-browser Llama 3 chatbot powered by WebGPU
I'm using flameshot ( https://flameshot.org/ ), which sounds pretty similar, but FOSS and cross platform.
- Flameshot: Free and open source screenshot software
-
Drawing app that came with Mint?
For your screenshots simply use Flameshot: https://flameshot.org
- Ask HN: What perfect software did you discover of recent?
-
lcd drawing tablet screen/pen viewport "mapped" over portion of screen, wayland
First, conceptually this is what I mean: think about when using a good screen-capture/annotation tool like flameshot: you select a region of the screen, and "magic" you can "edit" it, "in situ". No, what I'm talking about wouldn't share any of the same technical underpinnings with the way flameshot works, it would be the live monitor output, not a raster dump of the screen made to look like it's live. And the annotating would be done on a different screen. But as a user, this is pretty similar.
-
User Guides in Code Documentation: Empowering Users with Usage Instructions
Flameshot is a free and open-source screenshot tool for Linux that allows users to take screenshots of an area, a window or the full screen. It then provides an editor where users can modify the screenshots by drawing on them, adding text, highlighting areas, blurring parts and more. Users can save the screenshots in common image formats like PNG and JPEG, and upload them directly to image hosting sites like Imgur.
-
This guy just dropped the BEST MOD of the month and yall dont talk abt it ????
I would recommend Flameshot, available on Linux, Windows and Mac.
-
MSPaint like tool for Linux
This https://github.com/flameshot-org/flameshot/issues/1529 mat or may not be an issue for you with Flameshot, but it may be for others. It's solvable if it is an issue by using mandatory access control such as AppArmor or conditional build. Just FYI.
-
Thread Diario de Dudas, Consultas y Mitaps - 05/07
Flameshot viene con todo eso.
-
Screenshot in KDE Wayland is "off"
[3] https://github.com/flameshot-org/flameshot/issues/2848
What are some alternatives?
wain - WebAssembly implementation from scratch in Safe Rust with zero dependencies
shutter - Screenshot tool for Linux
rust-wasm - A simple and spec-compliant WebAssembly interpreter
ShareX - ShareX is a free and open source program that lets you capture or record any area of your screen and share it with a single press of a key. It also allows uploading images, text or other types of files to many supported destinations you can choose from.
wai - a wasm interpreter written by rust
ksnip - ksnip the cross-platform screenshot and annotation tool
tropy - Research photo management
greenshot - Greenshot for Windows - Report bugs & features go here: https://greenshot.atlassian.net or look for information on:
WasmCert-Isabelle - A mechanisation of Wasm in Isabelle.
wayland-protocols - Wayland protocol development (mirror)
simd-wasm-profiling - Exploring SIMD performance improvements in WebAssembly
sway - i3-compatible Wayland compositor