ESP-IDF
Espressif keeps five ESP-IDF branches alive and tells you almost nothing in the release notes.
Comparison · DevOps
pgRouting vs Erlang/OTP
A side-by-side editorial comparison of pgRouting and Erlang/OTP — release velocity, themes, recent moves, and the top alternatives to consider.
pgRouting vs Erlang/OTP: at a glance
What is pgRouting?
pgRouting 4.0 standardises output columns across its function catalog — a breaking cleanup.
The only visible activity is the pgRouting 4.0.0 pre-release chain: alpha1 in September, beta1 in October, rc1 in November. Alpha1 carries all the substance — the C++ standard moves to C++17, documentation for all four languages builds by default, and the function catalog gets a systematic pass in which output columns are standardised to a common shape and combinations signatures are promoted from proposed to official across the shortest-path family. The beta and candidate that follow only correct documentation about which functions are experimental, proposed or official.
What is Erlang/OTP?
Three OTP branches move as one release train, and SSH and epmd carry the security load.
Erlang/OTP is patching three branches in lockstep — 29 as current, 28 and 27 as maintenance — with each fix set published as a trio within minutes of itself. The window is dominated by security work in the network-facing applications: OTP 29.0.4 carried six CVEs including an epmd denial-of-service mitigation, and the 4 August trio brought SSH into line with RFC 4253 by rejecting packets not aligned to the cipher block size, with a timing-safe packet-discard path for CBC ciphers. A regression in the previous patch that stopped epmd binding to localhost was fixed in the same trio.
pgRouting vs Erlang/OTP: editorial side-by-side
pgRouting
0.0DEVOPS
pgRouting 4.0 standardises output columns across its function catalog — a breaking cleanup.
◆ Current state
The only visible activity is the pgRouting 4.0.0 pre-release chain: alpha1 in September, beta1 in October, rc1 in November. Alpha1 carries all the substance — the C++ standard moves to C++17, documentation for all four languages builds by default, and the function catalog gets a systematic pass in which output columns are standardised to a common shape and combinations signatures are promoted from proposed to official across the shortest-path family. The beta and candidate that follow only correct documentation about which functions are experimental, proposed or official.
◆ Where it's heading
This is a major version being spent on consistency rather than new algorithms. Standardising outputs to (seq, path_seq, start_vid, end_vid, node, edge, cost, agg_cost) across functions that previously each had their own column set is the kind of change that only happens at a major boundary, and promoting combinations signatures to official settles an API that has been provisional for years. The two releases after alpha1 changing nothing but function-status documentation suggests the classification of experimental versus official is itself the contested part of this release.
◆ Prediction
Expect 4.0.0 final to follow with little functional change beyond what alpha1 established, since both subsequent pre-releases were documentation-only. The absence of any release after rc1 in November is the notable gap — nothing in these entries explains it.
Erlang/OTP
5.0DEVOPS
Three OTP branches move as one release train, and SSH and epmd carry the security load.
◆ Current state
Erlang/OTP is patching three branches in lockstep — 29 as current, 28 and 27 as maintenance — with each fix set published as a trio within minutes of itself. The window is dominated by security work in the network-facing applications: OTP 29.0.4 carried six CVEs including an epmd denial-of-service mitigation, and the 4 August trio brought SSH into line with RFC 4253 by rejecting packets not aligned to the cipher block size, with a timing-safe packet-discard path for CBC ciphers. A regression in the previous patch that stopped epmd binding to localhost was fixed in the same trio.
◆ Where it's heading
The maintenance pattern is unusually strict: 27, 28 and 29 receive the same trouble reports on the same day, so the effective support window is wide and sites on older majors are not being pushed forward by security pressure. Where the fixes land is consistent — ssh, ssl, crypto, public_key and erts account for nearly every changed application across these releases, which is the distribution epmd and the TLS/SSH stack impose on a distributed runtime. The CBC timing mitigation in particular is an old class of attack being closed properly rather than papered over.
◆ Prediction
Expect the next patch trio to follow the same shape — a small set of trouble reports applied to all three branches simultaneously — with ssh and ssl the most likely applications to change. Nothing in these entries indicates feature work landing on the patch branches; that stays on the next major.
Alternatives to pgRouting and Erlang/OTP
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 pgRouting or Erlang/OTP.
Apache Seata
Seata's first Apache release is stuck in a voting round, two years after its last shipped version.
Apollo Config
Apollo is grinding down the operational cost of running a config service.
Dapr
Dapr patches three release lines at once and writes root-cause notes for each fix.
Apache bRPC
Apache bRPC keeps widening what it can talk to and what it can run on.
OpenTripPlanner
OpenTripPlanner finished a multi-year migration by deleting its REST API.
See all pgRouting alternatives → · See all Erlang/OTP alternatives →
Recent activity from pgRouting and Erlang/OTP
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoErlang/OTPSSH now rejects misaligned packets with a timing-safe discard
- 5d agoErlang/OTPOTP 28 takes the same SSH alignment and epmd fixes
- 5d agoErlang/OTPOTP 27 receives the same erts and ssh patches
- 12d agoErlang/OTP27 July patch touches crypto, ssl, ssh and public_key on OTP 28
- 12d agoErlang/OTPOTP 27 mirrors the 27 July crypto and transport patch
- 13d agoErlang/OTPOTP 29.0.4 carries six CVEs and an epmd DoS mitigation
- 9mo agopgRouting4.0.0 candidate updates experimental-function documentation
- 9mo agopgRouting4.0.0 beta fixes documentation of function maturity levels
- 10mo agopgRouting4.0.0 alpha standardises outputs and promotes combinations APIs ⚡
Frequently asked questions
What is the difference between pgRouting and Erlang/OTP?
They serve adjacent needs but don't currently overlap on shipped themes. Erlang/OTP is currently shipping more aggressively (velocity 5.0 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.
Is pgRouting better than Erlang/OTP?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Erlang/OTP is currently shipping more aggressively (velocity 5.0 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.
What are the best alternatives to pgRouting?
Top pgRouting alternatives in DevOps are ranked by recent ship velocity. Browse the "pgRouting alternatives" section above for the current picks, or visit /alternatives/pgrouting for the full list with editorial commentary on each.
What are the best alternatives to Erlang/OTP?
Top Erlang/OTP alternatives in DevOps are ranked by recent ship velocity. Browse the "Erlang/OTP alternatives" section above for the current picks, or visit /alternatives/erlang-otp for the full list with editorial commentary on each.