r/programming • • Aug 20 '20

Announcing TypeScript 4.0

https://devblogs.microsoft.com/typescript/announcing-typescript-4-0/
1.3k Upvotes

236 comments sorted by

View all comments

Show parent comments

100

u/crabmusket Aug 21 '20

IMO if you're not doing semver, do calendar versioning like Ubuntu (YY.MM) or dgraph.

13

u/BesottedScot Aug 21 '20

Always liked Ubuntu's versioning.

11

u/teszes Aug 21 '20

It also helps underline how out of date a version may be and if it needs to be updated.

"We are still on version 2002" hits harder than "version 3.4".

5

u/BesottedScot Aug 21 '20

Aye unless you're Microsoft and like to play guess what version of SQL you're on.

2

u/DreamyRustacean Aug 21 '20

OMG, my least favorite game! MS version numbers can die in a fire!

0

u/[deleted] Sep 14 '20

[deleted]

2

u/757DrDuck Sep 16 '20

TypeScript One 3.11 for Workgroups

4

u/Lafreakshow Aug 21 '20

Dunno, I always thought Semantic Versioning specially for projects with breaking changes regularly should be a thing.

I don't like their current system though, Major versions should be reserved for... well... major milestones like reaching the first full featured version or adding a major new feature or completely changing how the thing works. Kind of like a difference between breaking changes one could relatively easily migrate to and breaking changes would require significant work to migrate.

I guess simply leaving off the patch number of a semantic version would be pretty confusing but you get what I mean, a standardized, easily comparable way in the vein of semantic versioning but with only minor and major parts. It should probably have some kind of identifier so it's easy to differentiate from regular semantic versioning, especially since minor changes in semantic versioning shouldn't be breaking. maybe one could a a letter to the minor part or something like that. Like so: "1.b3.3". The "b" indicating a minor version that should be expected to contain breaking changes. Note that there is still a third part for non breaking patches but I would consider that optional.

I don't know if this goes completely against the idea behind semantic versioning, I also don't think it must be this, I'd just like a standard with similar adoption. Ubuntu's system is pretty robust too and if a standardized notation is set then it would be equally easy to compare versions with each other So maybe that can be the standard. In the end what I really want is a system that allows dependency management tools and programmers alike to see at a glance that minor versions may contain breaking changes, similar to how the semantic versioning standard tells us to expect breaking changes with major version. The form of this I don't really care about.

In the end, as long as the version keeps going up instead of down, I'm fine with it. It may be a bit inconvenient but it's like there's a risk to accidentally confuse a new release for an older one.

6

u/2Punx2Furious Aug 21 '20

(YY.MM)

But that's going to break in 80 years. Or sooner, for people who started using it in the 90s.

19

u/Zaneris Aug 21 '20

If your software is around long enough for this to become an issue, I think it would fall under the good problems to have category.

5

u/crabmusket Aug 21 '20

I suspect 20.04 will be out of LTS by the time 2120 rolls around!

0

u/[deleted] Aug 21 '20

[deleted]

3

u/hippydipster Aug 21 '20

Developer: Not my problem!
Aubrey De Gray: We've solved aging!
Developer: Fuck!

2

u/[deleted] Aug 21 '20

[removed] — view removed comment

2

u/2Punx2Furious Aug 21 '20

YYYY would work. At least for the next 8980 years.

2

u/GrandOpener Aug 21 '20

Longer than that actually since no existing software versions predate the mid 1900s.

2

u/GrandOpener Aug 21 '20

I was today years old when I finally learned what that weird .04 at the end of Ubuntu LTS versions means.

1

u/tHeSiD Aug 21 '20

I think they should go the ECMAscript way, TS4 = TS2020, TS5= TS2021 etc 🤓