CoolProp
CoolProp 8.0 bought sub-microsecond property lookups — and shipped a desktop app alongside it.
A side-by-side editorial comparison of Meilisearch and MMseqs2 — release velocity, themes, recent moves, and the top alternatives to consider.
A week of walking back v1.52.0 while the sharding work ships on a parallel tag
Meilisearch spent the last week stabilising rather than shipping. v1.52.0 introduced SSE routes for tasks and batches plus a formatting speedup, and all three of the patch releases that followed reverted pieces of it — the SSE routes in v1.52.2 and the search speedup in v1.52.3. Meanwhile v1.53.0 landed on the same day as those patches, carrying sharding support for foreign filters and new index-size stats.
MMseqs2 put homology search on GPUs, then spent two releases making it behave
Release 16 was the pivot: GPU-accelerated sensitive search on Turing-generation and newer CUDA hardware, shipped alongside a relicensing to MIT. The two releases since have been consolidation - Release 17 fixing GPU output corruption and a common prefilter crash, Release 18 restoring the custom substitution matrices that GPU support had cost users, making generated databases GPU-compatible, and adding a Forward-Backward aligner.
Meilisearch spent the last week stabilising rather than shipping. v1.52.0 introduced SSE routes for tasks and batches plus a formatting speedup, and all three of the patch releases that followed reverted pieces of it — the SSE routes in v1.52.2 and the search speedup in v1.52.3. Meanwhile v1.53.0 landed on the same day as those patches, carrying sharding support for foreign filters and new index-size stats.
The distributed-search work is the throughline: foreign filters can now resolve documents across the network under sharding, and their retrieval ceiling moved from 100 to 1000 documents. That extends the federated-fetch-across-shards direction Meilisearch set out earlier rather than opening a new one. The push-based task streaming is the unsettled part — it shipped as experimental, came out two releases later, and has not returned.
Expect the SSE task and batch streams to reappear once the underlying issue is resolved, since the routes were explicitly framed as experimental rather than withdrawn. The sharding surface looks likely to keep widening on the same incremental cadence.
Release 16 was the pivot: GPU-accelerated sensitive search on Turing-generation and newer CUDA hardware, shipped alongside a relicensing to MIT. The two releases since have been consolidation - Release 17 fixing GPU output corruption and a common prefilter crash, Release 18 restoring the custom substitution matrices that GPU support had cost users, making generated databases GPU-compatible, and adding a Forward-Backward aligner.
The arc is a research tool absorbing a hardware shift. Each GPU release trades something away and buys it back later: Release 16 dropped custom substitution matrices, Release 18 restored them through a new lambda calculator. Underneath that, MMseqs2 keeps serving as the engine other tools are built on - Foldseek and ColabFold features appear in its release notes before they appear anywhere else.
Expect GPU coverage to keep widening from search into the clustering and taxonomy workflows that still run on CPU, and the Forward-Backward aligner to gain the GPU path the rest of the alignment code now has. Further breaking database-format changes are likely as GPU compatibility propagates.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Meilisearch or MMseqs2.
CoolProp 8.0 bought sub-microsecond property lookups — and shipped a desktop app alongside it.
pymatgen split its core into a separate package without breaking a single import.
Uproot quietly made RNTuple the default write format — filed under 'chore'.
Awkward Array rewrote its kernels — 5x faster list reductions, and different layouts than before.
rioxarray is a thin, disciplined seam between rasterio and xarray — and stays that way.
Ten years in, SeqKit still ships by widening its flags rather than its scope.
See all Meilisearch alternatives → · See all MMseqs2 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Meilisearch is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Meilisearch is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Meilisearch alternatives in DevOps are ranked by recent ship velocity. Browse the "Meilisearch alternatives" section above for the current picks, or visit /alternatives/meilisearch for the full list with editorial commentary on each.
Top MMseqs2 alternatives in DevOps are ranked by recent ship velocity. Browse the "MMseqs2 alternatives" section above for the current picks, or visit /alternatives/mmseqs2 for the full list with editorial commentary on each.