Pak Alternatives

Similar projects and alternatives to pak

semver

720 7,008 2.3 pak VS semver

Semantic Versioning Specification
proposal-pipeline-operator

102 7,359 2.7 HTML pak VS proposal-pipeline-operator

A proposal for adding a useful pipe operator to JavaScript.
WorkOS

workos.com
sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
endoflife.date

43 2,173 9.9 Ruby pak VS endoflife.date

Informative site with EoL dates of everything
libc

10 1,954 9.4 Rust pak VS libc

Raw bindings to platform APIs for Rust
ROM

5 2,063 5.7 Ruby pak VS ROM

Data mapping and persistence toolkit for Ruby
proposal-Array.prototype.includes

4 141 0.0 HTML pak VS proposal-Array.prototype.includes

Discontinued Spec, tests, reference implementation, and docs for ESnext-track Array.prototype.includes
pragmaticversioning

4 90 6.6 HTML pak VS pragmaticversioning

Pragmatic versioning optimizes for communicating changes to a package to package consumers, while retaining simple semantics for package maintainers.
InfluxDB

www.influxdata.com
sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
comver

3 - - pak VS comver
imver

1 5 10.0 pak VS imver

Immutable Versioning Specification

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better pak alternative or higher similarity.

Suggest an alternative to pak

pak reviews and mentions

Posts with mentions or reviews of pak. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-03.

Pragmatic Versioning – An Alternative to Semver
9 projects | news.ycombinator.com | 3 Dec 2023

From your issue link:
> Then commons-logging changes its API incompatibly and is released as commons-logging 2.0.1. Authentication adopts commons-logging 2.0.1 while other libraries still depend on 1.1.1
> Now my-application is broken, because the dependency tree includes two versions of commons-logging which share packages, class / functions names, and thus can not be loaded simultaneously.
I absolutely don't see how this is a problem with semver, it is not the responsibility of semver to tell a language how packages should be isolated and loaded. That is a problem of a) the language and b) dependency resolution in the package manager.
> SemVer is a product of Ruby community.
Bundler, by design, does not allow the above, instead having a flat, consistent vision of dependencies.
NPM though, allows that, allowing nested dependencies, by virtue of the ES6 module system importing to a variable in a lexical scope. Go also allows that, by virtue of its imports being scoped to a package (or file, I can't recall).
Ruby can do that kind of isolation too. In fact, I've done it: https://github.com/lloeki/pak
Unless packages leak to globals each version is oblivious to the one next to it. Unless package dependents communicate with one another using objects from the packages they can happily live in their own world. Now if they do, then it's like hitting a HTTP /api/v1 with an HTTP /api/v2 client and somehow wishing things will work. Either the package (which should not leak globals / disallow cross-version communication) or the language (which should not allow leaking globals / detect incompatible communication).
None of this is the responsibility of semver.
Rails is not written in Ruby
4 projects | news.ycombinator.com | 4 Feb 2022

(the link jumps to some random place for me)
Well, you always could, it was just a bit more involved:
https://github.com/lloeki/pak