AVIF, WebP, PNG, JPEG: A Practical Image Format Guide for 2026

·1 views

A developer who spent two years building an image compression tool has shared a practical guide comparing the four major image formats. PNG is best for graphics with sharp edges or transparency, while JPEG remains universally compatible for photos despite lacking transparency support. WebP offers a strong middle ground, producing files 25–35% smaller than JPEG at equivalent quality with both lossy and lossless support. AVIF, the newest format, goes further with files up to 50% smaller than JPEG and support for HDR and 12-bit color, though it requires fallback options for older browsers. In real-world tests on a single photo, JPEG produced an 842 KB file, WebP came in at 547 KB, and AVIF was the smallest at 382 KB.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Machines dominate Bitcoin's OP_RETURN data, outwriting humans 45 to 1

A full census of every OP_RETURN output on the Bitcoin blockchain, from the genesis block to block 958,893, reveals that human-readable messages have never been the majority of data written to the chain. The Runes token protocol alone, launched at the April 2024 halving, generated 171 million OP_RETURN outputs in roughly two years — about 45 times more than all human-readable messages in Bitcoin's entire history. Even at peak human activity during the BRC-20 boom era, human-readable text accounted for only 13.5% of OP_RETURN outputs. Before Runes, binary timestamping protocols like Veriblock and OMNI dominated, comprising over 98% of pre-ordinals OP_RETURN data. The findings suggest Bitcoin's data-carrier space has always been machine-driven, with the dominant user shifting from timestamping protocols to token-minting engines rather than from humans to machines.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Mingxin FX100 Hits 90% Line-Rate on 100GbE, Easing LLM Inference Bottlenecks

Mingxin's FX100 all-flash NVMe-oF storage array achieved roughly 90% line-rate utilization on a single 100GbE port in benchmark tests, delivering approximately 11.25 GB/s of effective bandwidth. This figure is 60–80% higher than the sequential read speed of a typical single PCIe Gen4 NVMe drive, effectively removing the network as a primary bottleneck in LLM inference workloads. In long-context deployments involving a 480-billion-parameter model running on eight GPUs, FX100 cut median time-to-first-token by 26–32% compared to baseline storage configurations. When paired with LMCache's parallel read-patching in a single-card, 16-concurrency cold-read test using Qwen2.5-32B, TTFT dropped from 37.97 seconds to 9.30 seconds — a 4.1x improvement — while bandwidth rose 5.3x to 5.23 GB/s. The results suggest that high port utilization allows concurrent GPU requests to avoid bandwidth contention, enabling inference frameworks such as vLLM to access remote KV Cache with latency approaching that of local storage.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer ports Rust KVM hypervisor to ARM64, resolves boot errors to run binaries

A developer working on a Rust-based KVM hypervisor documented the process of porting it to ARM64 architecture, encountering an ENOEXEC error when attempting to access CPU registers via KVM_GET_ONE_REG. Tracing the error through Linux kernel source code on Bootlin Elixir revealed that the vCPU must be initialized via KVM_ARM_VCPU_INIT before register access is permitted. To determine the correct initialization parameters, the developer used a GDB script to intercept and decode the ioctl call from a reference implementation, extracting the target value of 5 and zeroed feature flags. After implementing KVM_ARM_VCPU_INIT in Rust with these values, register get and set operations began working correctly. The developer then tackled a further issue where KVM_RUN never returned, experimenting with signal handlers to interrupt execution and retrieve register state synchronously.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

TypeScript 6.0 --noEmit Flag Can Cut CI Build Times by Up to 80%

TypeScript 6.0 introduces a build approach where the compiler is used solely for type-checking rather than code generation, enabled by the --noEmit flag. This configuration prevents tsc from writing output files, allowing it to complete type validation 40-60% faster by skipping transformation and file I/O. Modern bundlers like esbuild and swc, which strip TypeScript syntax 10-20 times faster than tsc transpiles, can then handle code generation in parallel. Running type-checking and transpilation concurrently in CI pipelines can reduce total build times by 60-80% without compromising type safety. The trade-off is that declaration files for libraries still require tsc output, but application builds no longer need to invoke the compiler's emit logic.

0 comments Read more at DEV Community