Snappy
nim_emscripten_tutorial
| Snappy | nim_emscripten_tutorial | |
|---|---|---|
| 5 | 2 | |
| 5,994 | 78 | |
| 0.6% | - | |
| 5.2 | 10.0 | |
| 17 days ago | over 1 year ago | |
| C++ | JavaScript | |
| GNU General Public License v3.0 or later | MIT License |
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.
Snappy
-
Why I enjoy using the Nim programming language at Reddit.
Another example of Nim being really fast is the supersnappy library. This library benchmarks faster than Google’s C or C++ Snappy implementation.
-
Stretch iPhone to Its Limit: 2GiB Stable Diffusion Model Runs Locally on Device
It doesn't destroy performance for the simple reason that nowadays memory access has higher latency than pure compute. If you need to use compute to produce some data to be stored in memory, your overall throughput could very well be faster than without compression.
There have been a large amount of innovation on fast compression in recent years. Traditional compression tools like gzip or xz are geared towards higher compression ratio, but memory compression tends to favor speed. Check out those algorithms:
* lz4: https://lz4.github.io/lz4/
* Google's snappy: https://github.com/google/snappy
* Facebook's zstd in fast mode: http://facebook.github.io/zstd/#benchmarks
-
Compression with best ratio and fast decompression
Google released Snappy, which is extremely fast and robust (both at compression and decompression), but it's definitely not nearly as good (in terms of compression ratio). Google mostly uses it for real-time compression, for example of network messages - not for long-term storage.
-
How to store item info?
Just compress it! Of course if you will you ZIP, players will able to just open this zip file and change whatever they want. But you can use less popular compression algorithms which are not supported by default Windows File Explorer. Snappy for example.
- What's the best way to compress strings?
nim_emscripten_tutorial
-
Why I enjoy using the Nim programming language at Reddit.
Cross-platform usually gets you the standard Windows / Linux / macOS, however Nim does not stop there. Nim can even run on mobile iOS and Android and has two different modes for the web - plain JavaScript or WASM.
-
Bun v0.2.0
I believe cyclic imports are coming. And Nim does supports wasm...you can target it with `--cpu:wasm32`. You most likely want to pair that with emscripten as in https://github.com/treeform/nim_emscripten_tutorial
What are some alternatives?
zstd - Zstandard - Fast real-time compression algorithm
shady - Nim to GPU shader language compiler and supporting utilities.
LZ4 - Extremely Fast Compression algorithm
jsony - A loose, direct to object json parser with hooks.
brotli - Brotli compression format
zig - The version of Zig used by Bun. Not a fork! Just a slightly older version.
ZLib - A massively spiffy yet delicately unobtrusive compression library.
glfm - Wrapper of GLFM (OpenGL ES and input for iOS and Android) library for Nim.
LZMA - (Unofficial) Git mirror of LZMA SDK releases
bench - 📊 Comparing deno, node and bun HTTP frameworks
zlib-ng - zlib replacement with optimizations for "next generation" systems.
zippy - Pure Nim implementation of deflate, zlib, gzip and zip.