Porffor: A from-scratch ahead-of-time JS engine

Re:Porffor: A from-scratch ahead-of-time JS engine by canadahonk on Tuesday July 30, 2024 @07:22PM (#41115077)

Exactly. The versioning system is definitely unique and controversial, but I think it fits for a fast moving project like this, so I don't have to really consider versioning which could slow development. When it becomes more stable, I'll likely move to a more traditional semver scheme from 1.0.

[ Parent | on HN ]

Re:Porffor: A from-scratch ahead-of-time JS engine by apgwoz on Wednesday July 31, 2024 @08:40PM (#41125097)

What happens if there’s a regression in coverage, maybe due to a large sweeping change, and you go from 0.40 -> 0.35 ?

[ Parent | on HN ]

Re:Porffor: A from-scratch ahead-of-time JS engine by astrobe_ on Thursday August 01, 2024 @03:32AM (#41126937)

There's the commit hash. Basically the "version number" is the commit hash, the human-generated (version) numbers added to it are merely progress indicators, which might be randomly useful. But for a project that has 1 branch, 0 tags and nearly 2000 commits, that's not really important.

[ Parent | on HN ]

Re:Porffor: A from-scratch ahead-of-time JS engine by apgwoz on Thursday August 01, 2024 @10:20AM (#41129371)

yes, the entire exercise isn’t important. It just breaks the monotonicity that version numbers typically have. At that point, just call your version <progress>.sha

[ Parent | on HN ]