← Back to home
Comparison · DevOps

Erlang/OTP vs Liquidsoap

A side-by-side editorial comparison of Erlang/OTP and Liquidsoap — release velocity, themes, recent moves, and the top alternatives to consider.

Erlang/OTP vs Liquidsoap: at a glance

FeatureErlang/OTPLiquidsoap
SectorDevOpsDevOps
Velocity score5.06.3
Sparks · 30d01
Top themesruntime, security, ssh, tlsaudio-streaming, subtitles, icecast, ocaml
Last editorial update9d ago2h ago
WebsiteVisit →Visit →

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.

Read the full Erlang/OTP trajectory →

What is Liquidsoap?

Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own

The 2.5.x rolling release carries the accumulated 2.5.0 changelog, and it is the largest body of work Liquidsoap has staged in over a year. Subtitles become a dedicated content type alongside audio and video, with native SRT decoding, FFmpeg subtitle encode and decode, bitmap passthrough, callbacks, transformations and dynamic insertion. An Icecast-compatible server ships as icecast.server, with source authentication, mount points, relay and per-listener encoding. Underneath, the source composition model was rewritten: switch, fallback, rotate and random drop their parallel list parameters for per-source methods, and switching now fades by default.

Read the full Liquidsoap trajectory →

Erlang/OTP vs Liquidsoap: editorial side-by-side

E5.0

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.

L6.3

Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own

◆ Current state

The 2.5.x rolling release carries the accumulated 2.5.0 changelog, and it is the largest body of work Liquidsoap has staged in over a year. Subtitles become a dedicated content type alongside audio and video, with native SRT decoding, FFmpeg subtitle encode and decode, bitmap passthrough, callbacks, transformations and dynamic insertion. An Icecast-compatible server ships as icecast.server, with source authentication, mount points, relay and per-listener encoding. Underneath, the source composition model was rewritten: switch, fallback, rotate and random drop their parallel list parameters for per-source methods, and switching now fades by default.

◆ Where it's heading

Liquidsoap is expanding on two axes at once. It is broadening what a stream can carry - subtitles are a third content modality in a system that has understood two - and it is moving up the stack from a source that feeds Icecast into something that can be the Icecast. The language work points the same way: a source(_) type for unknown content, callback release semantics, and effect-scoped clocks are the kind of changes made when scripts are getting large enough that lifetime and typing errors cost real production time.

◆ Prediction

The 2.5.0 final should follow the rolling branch within a release cycle, and the migration guide already shipped for the composition parameter changes suggests the breaking surface is considered settled. Watch whether subtitle support reaches the harbor and Icecast server paths, which the current notes do not say.

Alternatives to Erlang/OTP and Liquidsoap

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 Erlang/OTP or Liquidsoap.

See all Erlang/OTP alternatives → · See all Liquidsoap alternatives →

Recent activity from Erlang/OTP and Liquidsoap

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 14h agoLiquidsoapSubtitles become a content type and Liquidsoap ships its own Icecast server
  2. 9d agoLiquidsoapLiquidsoap Rolling Release 2.4.x
  3. 14d agoErlang/OTPSSH now rejects misaligned packets with a timing-safe discard
  4. 14d agoErlang/OTPOTP 28 takes the same SSH alignment and epmd fixes
  5. 14d agoErlang/OTPOTP 27 receives the same erts and ssh patches
  6. 22d agoErlang/OTP27 July patch touches crypto, ssl, ssh and public_key on OTP 28
  7. 22d agoErlang/OTPOTP 27 mirrors the 27 July crypto and transport patch
  8. 22d agoErlang/OTPOTP 29.0.4 carries six CVEs and an epmd DoS mitigation
  9. 2mo agoLiquidsoapQueue removal commands and O(1) clock propagation in Liquidsoap 2.4.5
  10. 4mo agoLiquidsoapLiquidsoap 2.4.4 supersedes 2.4.3 days after release
  11. 4mo agoLiquidsoapRaw string literals arrive in Liquidsoap 2.4.3
  12. 7mo agoLiquidsoapLiquidsoap 2.4.1 opens the stabilization phase

Frequently asked questions

What is the difference between Erlang/OTP and Liquidsoap?

They serve adjacent needs but don't currently overlap on shipped themes. Liquidsoap is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Erlang/OTP better than Liquidsoap?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Liquidsoap is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 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.

What are the best alternatives to Liquidsoap?

Top Liquidsoap alternatives in DevOps are ranked by recent ship velocity. Browse the "Liquidsoap alternatives" section above for the current picks, or visit /alternatives/liquidsoap for the full list with editorial commentary on each.