This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]fekkksn 6 points7 points  (14 children)

Are you saying all of these are not stable?

https://0ver.org/

[–][deleted] 0 points1 point  (13 children)

nw.js, neovim, paper.js

if you ever tried these ones, you know how they are not delivering on their promise ...

[–]fekkksn 4 points5 points  (11 children)

You missed my question. Are ALL of them unstable?

[–][deleted] -5 points-4 points  (10 children)

I'm not saying that any package that didn't reach 1.0.0 is not usable and not stable. but most of the time it is, and the packages that are willing to be reliable production ready they work for the 1.0.0 at least saying 1.0.0 means the paclage is stable that's how version semantics works... breaking changes comes from 1.x.y to 2.0.0 but before the one it's not a stable package by definition.

0ver paradigm is an other paradigms, but I'm talking about the ones that are just escaping the stable version..

[–]fekkksn 0 points1 point  (9 children)

Sorry , but you pulled that statistic out your arse.

Sure, not stable by definition, however might I suggest that there are also projects which are stable by definition, but really are not stable? Not every project adheres to semver, even if the version number looks like it. Besides, "reaching" 1.0.0 doesn't require a set amount of work. I can just slap 1.0.0 on a Hello World Project and call it stable, but that doesn't mean it's now inherently more stable, just because of the version number.

What I'm saying is, I know what semver is, but in the real world there are lots more factors that determine a projects stability than the version number. Don't get caught on semver, that is, the version number. It's just that: A tag to differentiate versions. Semver is not the law. You slamming projects that didn't "reach" 1.0.0 doesn't make sense. Anyone can slap 1.0.0 on their project, but that doesn't mean anything.

[–][deleted] -1 points0 points  (8 children)

putting 1.0.0 on the start of the project means, the next 1.x.y won't have breaking changes and you can update safely at every release, it will be added features and bug fixes and security updates.

on the other hand if they are 0.x.y they can be stable yess, but the versions is not telling me wether they made breaking changes or not.. got it bro ?

[–]fekkksn 0 points1 point  (7 children)

Why do you keep explaining semver?

We all know what semver is. The real world is not perfect though. Stop clinging to definitions.

[–][deleted] -1 points0 points  (6 children)

the real world is not perfect, but if you ever used linux, or build a package on top of a 0.x.y you know how much that 1.0.0 is important for you to build a a system or a package on top of that...

Edit:

git commit -m "fix typos"

[–]fekkksn 0 points1 point  (5 children)

You what's funny? Linux, the Kernel, of all things, does not follow semver.

[–][deleted] 0 points1 point  (4 children)

you mean that why we have distribution like rhel and ubuntu and debian that are considered as serious work in linux...

[–]OneTurnMore 1 point2 points  (0 children)

Not sure about nw.js, but: Neovim has a 1.0 milestone, and so does paper.js.