CRoaring
libvips
CRoaring | libvips | |
---|---|---|
8 | 24 | |
1,456 | 9,029 | |
1.6% | 1.1% | |
8.9 | 9.2 | |
1 day ago | 3 days ago | |
C | C | |
GNU General Public License v3.0 or later | GNU Lesser 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.
CRoaring
-
(Don't) crank up the warnings to 11
The PR in question seems to be https://github.com/RoaringBitmap/CRoaring/pull/446
I agree that the GitHub analyses are worse than useless, but I also think it highlights the friction between intrinsics and the program in which they appear. There probably is a better model.
-
Progress in building an 100% rust lang program.
Installation completed the program build successfully!! https://www.reddit.com/r/openbsd/comments/yux513/comment/iwbm72c/?context=3 I configured 2 different files in .cargo (thanx @ivan_linux for https://github.com/RoaringBitmap/CRoaring/pull/412) and .profile ( https://rust-lang.github.io/rust-bindgen/requirements.html#openbsd ) But when I try to start the program unfortunately the node not starting and I get the following errors.
- I will need your help to complete (if possible) a rust lang program installation
- What std::bitset could have been
-
How do Games manage NPC schedules?
I use a fake database paired with compressed bits for flags and integer compression for various other traits. They follow a navigation guide similar to wind for foliage.
-
Help with CFFI, C struct decoding, best practices / portability
I've been using CFFI to access the CRoaring C API to Roaring Bitmaps. It's been pretty easy so far. However I'm not experienced in lisp FFI, and I'm unsure of the way to go about the task of decoding a C structure used for iteration in the C CPI. The structure is as follows: ``` typedef struct roaring_uint32_iterator_s { const roaring_bitmap_t *parent; // owner int32_t container_index; // point to the current container index int32_t in_container_index; // for bitset and array container, this is out // index int32_t run_index; // for run container, this points at the run
-
FFI advice sought
I have a build shared library build of the C API for Roaring Bitmaps and I'm just trying to figure out the right path forward to write a lisp interface to it on sbcl.
-
C Deep
CRoaring - C implementation of Roaring bitmaps. Apache-2.0
libvips
-
Ask HN: How to handle user file uploads?
Read through the comments and was surprised no one mentioned libvips - https://github.com/libvips/libvips. At my current small company we were trying to allow image uploads and started with imagemagick but certain images took too long to process and we were looking for faster alternatives. It's a great tool with minimum overhead. For video thumbnails, we use ffmpeg which is really heavy. We off-load video thumbnail generation to a queue. We've had great luck with these tools.
-
Building an online image compressor
After some research, I found libvips, a demand-driven, horizontally threaded image processing library. It is designed to run quickly while using as little as memory as possible.
- Libvips: A fast image processing library with low memory needs
-
Things you might not know about Next Image
Sharp is a fast and efficient image optimization Node.js module that makes use of the native libvips library.
-
Go Image Converting
h2non/bimg can handle both if the underlying libvips is compiled with support for both formats.
-
.Webp is the bane of my existence
if you're using linux (which it doesn't seem so) there's also vispdisp https://github.com/jcupitt/vipsdisp which is based on https://github.com/libvips/libvips which will likely take over how images are decoded in the future for everything, at least methodology wise.
-
How are responsive image sets are generated, stored, and managed server-side?
The magic happens by way of a library called Libvips, which contains an ultra-high-speed low-memory image resizer.
-
imagor v1 - a fast, Docker-ready image processing server in Go, libvips and more
imagor uses one of the most efficient image processing library libvips. It is typically 4-8x faster than using the quickest ImageMagick and GraphicsMagick settings.
-
[OSError] Cannot find pyvips library (DLLs)
Try the solutions here: https://github.com/libvips/libvips/issues/2479
-
Image library for fast read of huge Tif files?
in that case maybe take a look at https://github.com/libvips/libvips
What are some alternatives?
ZLib - A massively spiffy yet delicately unobtrusive compression library.
OpenCV - Open Source Computer Vision Library
C-album - An album of C code to study and investigate.
imagick - Go binding to ImageMagick's MagickWand C API
TurboPFor - Fastest Integer Compression
sharp - High performance Node.js image processing, the fastest module to resize JPEG, PNG, WebP, AVIF and TIFF images. Uses the libvips library.
better_bitset - A better `std::bitset` that supports scanning for bits optimally
GD - GD Graphics Library
gvsbuild - GTK stack for Windows
tesseract-ocr - Tesseract Open Source OCR Engine (main repository)
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
FreeImage - A custom distribution of FreeImage, with a CMake-based build system. Used by the Athena Game Framework.