Apache Pinot
Pinot 1.6 adds SQL DDL and vector backends, and now needs Java 25 to run its services.
Comparison · Infra & APIs
runc vs Scalar
A side-by-side editorial comparison of runc and Scalar — release velocity, themes, recent moves, and the top alternatives to consider.
runc vs Scalar: at a glance
What is runc?
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
What is Scalar?
Scalar is testing demand for hosting from inside localhost
The October 1.76 run put a sticky developer toolbar above the API reference on localhost, with Configure, Share, Deploy and Generate SDK tools in a side panel. The Deploy tool now shows a waitlist for API hosting on Scalar, and 1.76.4 records the server framework with each sign-up. AsyncAPI rendering kept improving, with binding schemas shown as structured properties. In another package line, 0.20.0 moved to Undici 8 with HTTP/2 on by default and raised the minimum Node.js version to 22.19.0.
runc vs Scalar: editorial side-by-side
runc
2.5INFRA · APIS
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
◆ Current state
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
◆ Where it's heading
The project keeps converting silent behaviour into explicit behaviour. Read-only requests that were ignored now fail, a umask that was dropped is now honoured, and poststart hooks moved to conform to the runtime spec. The same maintainers are shrinking the surface underneath, dropping the deprecated API and the high-level cilium/ebpf path, which took roughly 7.5% off the 1.5.2 binary. Stricter behaviour plus a smaller dependency set is what a component under every container host would be expected to do between majors.
◆ Prediction
1.5.0's notes pointed to a 1.6.0 in late October 2026, and the feed so far shows only rc.1, so further release candidates or the final are the next entries to expect. The refused read-only configurations are the change most likely to surface as user reports during testing.
Scalar
5.0INFRA · APIS
Scalar is testing demand for hosting from inside localhost
◆ Current state
The October 1.76 run put a sticky developer toolbar above the API reference on localhost, with Configure, Share, Deploy and Generate SDK tools in a side panel. The Deploy tool now shows a waitlist for API hosting on Scalar, and 1.76.4 records the server framework with each sign-up. AsyncAPI rendering kept improving, with binding schemas shown as structured properties. In another package line, 0.20.0 moved to Undici 8 with HTTP/2 on by default and raised the minimum Node.js version to 22.19.0.
◆ Where it's heading
The reference is becoming a dev-time workbench, not only a published page. Tools that sat in dropdowns moved to a persistent panel, and SDK generation was consolidated there. The hosting waitlist is the commercial signal: Scalar is collecting framework data from developers at the moment they run their API locally, which gives it a demand measure before committing to a deployment flow. AsyncAPI work remains the other steady investment.
◆ Prediction
Expect the waitlist to turn into a hosting beta, with the first supported frameworks chosen from the data 1.76.4 collects; FastAPI, Hono and Express are already named for detection. The monorepo's patch cadence should otherwise continue daily or near it.
Alternatives to runc and Scalar
Other Infra & APIs 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 runc or Scalar.
Greenbone Vulnerability Manager
Greenbone's gvmd starts on Active Directory credentials as report exports settle.
Bugsnag
Bugsnag names GraphQL operations and lets iOS teams attach context to app hangs.
ManageEngine Applications Manager
ManageEngine Applications Manager adds GaussDB monitoring and deepens APM Insight alarms.
Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Okta
Okta adds TypeScript to its Cross App Access guides and dates the end of Classic Engine features
Recent activity from runc and Scalar
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoScalarHosting waitlist now records the server framework
- 4d agoScalarDownloaded OpenAPI files named after the document title
- 5d agoScalarAsyncAPI schema rendering and a hosting waitlist on localhost
- 5d agoScalarSticky localhost toolbar with side panel and Deploy waitlist
- 10d agoScalar1.76.0 (2026-10-23)
- 10d agoScalar1.1.43 (2026-10-23)
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 4mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
- 4mo agoruncCVE-2026-41579: /dev symlink host write access fixed
- 4mo agoruncRelease candidate carrying the CVE-2026-41579 fix
Frequently asked questions
What is the difference between runc and Scalar?
They serve adjacent needs but don't currently overlap on shipped themes. Scalar is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 runc better than Scalar?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Scalar is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to runc?
Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.
What are the best alternatives to Scalar?
Top Scalar alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Scalar alternatives" section above for the current picks, or visit /alternatives/scalar for the full list with editorial commentary on each.