That's because nginx doesn't break things for end user every release, so there is no reason to bump major version.
replyI bet nginx doesn't even follow semantic versioning, which you seem to be talking about.
replyDon't have to bet: Nginx doesn't follow it. It has its own linux-kernel (odd vs evens) inspired convention.
replyDoesn't change the fact that only "breaking" changes in 1.x.x line are changes to defaults.
anyone can choose any version string convention they want for their project. Comparing two different pieces of software by their version string doesn't make sense.
replyOnly 19?
replyThe venerable unix tool "less" is on v701 and was probably already over 300 before react was born
I guess someone need to update https://0ver.org/ then.
replydeleted
replyGuys, this is what happens when you .useEffect()
replyI chalk that up more to different versioning schemes rather than how much work is being done. If nginx changed whole numbers like react did, I bet it would be even higher.
replylighttpd still around too, on 1.4.82, not too much changed there.
replyThey've been working on version 2.0 for many years now as well, I wonder when they think a release might happen.
reply> not necessarily in a good way
replyHow do you think versioning works? You know that it's completely arbitrary and up to the author, right? Very ironic comment.
deleted
reply